Configure kafka and kazoo loggers in contrail-alarm-gen
When contrail-alarm-gen disconnects from kafka, it retries
to reconnect to it and spits out bunch of messages. The kafka
python library logger was configured to output those messages
to stdout and due to this supervisor-analytics would get very
busy and not be able to handle other commands like stop all
and hence service supervisor-analytics stop would hang. Fix is
to configure the kafka and kazoo loggers in contrail-alarm-gen
as per the logging parameters and log to the file instead.
Reviewed: https:/ /review. opencontrail. org/34490 github. com/Juniper/ contrail- controller/ commit/ d235608dd6b5084 a20b2a80f1ed322 86e3e20263
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R3.1
commit d235608dd6b5084 a20b2a80f1ed322 86e3e20263
Author: Megh Bhatt <email address hidden>
Date: Fri Aug 11 11:14:35 2017 -0700
Configure kafka and kazoo loggers in contrail-alarm-gen
When contrail-alarm-gen disconnects from kafka, it retries analytics would get very analytics stop would hang. Fix is
to reconnect to it and spits out bunch of messages. The kafka
python library logger was configured to output those messages
to stdout and due to this supervisor-
busy and not be able to handle other commands like stop all
and hence service supervisor-
to configure the kafka and kazoo loggers in contrail-alarm-gen
as per the logging parameters and log to the file instead.
Change-Id: I553c53b3b54926 9a8cc0a87feda13 7980f008643
Closes-Bug: #1706832