Hi Yuan, please compare similar issue described in this bug report [1] and the corresponding fix [2]. 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. Witek [1] https://storyboard.openstack.org/#!/story/2001386 [2] https://review.openstack.org/525669 From: yuan....@t-systems.com [mailto:yuan....@t-systems.com] Sent: Freitag, 12. Januar 2018 19:36 To: roland.hochm...@hpe.com Cc: Bedyk, Witold <witold.be...@est.fujitsu.com>; mona...@lists.launchpad.net; Trebski, Tomasz <tomasz.treb...@ts.fujitsu.com>; bradley.kl...@charter.com Subject: alarm transition events are missing in kafka queue - mysql alarm state is updated properly Hi Roland, 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. Best Regard, Yuan Pen 571-594-6155
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
