[openstack-dev] [monasca] RE: alarm transition events are missing in kafka queue - mysql alarm state is updated properly
witold.bedyk at est.fujitsu.com
Mon Jan 15 14:03:16 UTC 2018
please compare similar issue described in this bug report  and the corresponding fix .
As Craig explained in his comment to patch set 4, Kafka server closes idle connections after around 10 minutes, which causes first write to the topic fail.
I hope it helps.
From: Yuan.Pen at t-systems.com [mailto:Yuan.Pen at t-systems.com]
Sent: Freitag, 12. Januar 2018 19:36
To: roland.hochmuth at hpe.com
Cc: Bedyk, Witold <witold.bedyk at est.fujitsu.com>; monasca at lists.launchpad.net; Trebski, Tomasz <Tomasz.Trebski at ts.fujitsu.com>; bradley.klein at charter.com
Subject: alarm transition events are missing in kafka queue - mysql alarm state is updated properly
This is Yuan Pen from Deutsche Telekom. I am sending this email to the monasca community asking for help on monasca threshold engine. We have found that when sometime alarm state transitions happened, the threshold engine updated mysql alarm state properly, but failed to put state transition events in kafka queue (alarm-state-transitions). Does this ring a bell to anyone in the community? If this is a real problem, is there anything we can do to make sure the event in transition queue and state in mysql is synched? Any comments or help are greatly appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev