data_engine stops processing all qos_processor enriched metrics after restart

book

Article ID: 188206

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction


If the data_engine is restarted after qos_processor has updated the origins, the data_engine, no longer databases these metrics and errors:


Feb 28 07:54:07:384 [2556] 0 de: QoSInsert::InsertData Failed to create data object in DB.  id=-1 defid 14 qos=QOS_DISK_USAGE
Feb 28 07:54:07:384 [2556] 0 de: ADO_QoSInsert::InsertQosObjectEx - exists already qos=QOS_DISK_USAGE_PERC, source=Agentless-10.74.136.220, target=/dev/shm 
Feb 28 07:54:07:385 [2556] 0 de: QoSInsert::CreateQoSObjectDB - QoS object creation failed, unknown reaso

Cause

The root cause of this issue is that the checksum field in S_QOS_DATA table used to be evaluated based on source, target, and origin. Later on, in recent release (9.2.0) origin is also part of the calculating checksum.



The qos_processor in this case only updates the origin field in S_QOS_DATA but checksum is not reevaluated/updated based on new origin.



On restart of data_engine the checksum evaluated from data_engine(based on new origin) is different then checksum in the database and hence the data_engine throws this exception.

Environment

Release : 9.2.0

Component : UIM - QOS_PRROCESSOR, UIM - DATA_ENGINE

Resolution


This is fixed in data_engine-9.20HF5