When Ceilometer Middleware is integrated with SWIFT, some of user requests hangs at ceilometer level.
When we debugged firther, to identify where the requests are stuck, it is observed that the following call of oslo_messaging Notifier class does not return.
the call "self._notifier.info" does not return in some case and due to this, the user requests are stuck indefinitely.
It is confirmed that there is no problem with RabbitMQ server or ceilometer server as both of them are accessible from other SWIFT cluster at the time problem is observed on different setup.
When Ceilometer Middleware is integrated with SWIFT, some of user requests hangs at ceilometer level.
When we debugged firther, to identify where the requests are stuck, it is observed that the following call of oslo_messaging Notifier class does not return.
{code} Notifier( get_transport( cfg.CONF, url=conf. get('url' )), id='ceilometerm iddleware' , conf.get( 'driver' , 'messagingv2'), get('topic' , 'notifications')) info(context. get_admin_ context( ).to_dict( ), http.request' , event.as_dict())
47 import oslo_messaging
....
121 self._notifier = oslo_messaging.
122 oslo_messaging.
123 publisher_
124 driver=
125 topic=conf.
126
....
283
284 self._notifier.
285 'objectstore.
286
{code}
the call "self._ notifier. info" does not return in some case and due to this, the user requests are stuck indefinitely.
It is confirmed that there is no problem with RabbitMQ server or ceilometer server as both of them are accessible from other SWIFT cluster at the time problem is observed on different setup.