amarnathreddy created AMBARI-20157:
--------------------------------------
Summary: Ambari sends SNMP notifications in incorrect order
Key: AMBARI-20157
URL: https://issues.apache.org/jira/browse/AMBARI-20157
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.2
Reporter: amarnathreddy
Priority: Minor
Ambari sends notifications in wrong order. ideally first generated Alert should
be notified first.
This issue is reproducible in straight steps.
1. Have 4 to 5 alerts generated in short span of time.
2. when Ambari notifier thread queries Database with the query like "select *
from alert_notice where notify_state = 'PENDING'"
This query returns last one first.
Ex:
2066 51 4876 PENDING a11bffc9-3eda-42a7-b8ef-3f197cddfa26
2065 51 4874 PENDING 05e810cd-61a0-4d5c-9687-334aa71e0aaa
2064 51 4875 PENDING b30999d3-0c78-46a3-aca4-f035743030b8
2063 51 4873 PENDING 9508afee-48dd-4599-a901-8d64ee07b909
2062 51 4872 PENDING 73d02181-138a-440e-8e8e-32f7ac5fbe2e
2061 51 4871 PENDING 42a134f0-f979-4be3-a51d-a5f804a11c89
So Notified threads loops that list and sends one by one.
This needs to be fixed. either have to read " order by notification_id" so that
it gives correct order.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
