Ceilometer backend can hang if started before mongo cluster starts

Bug #1519153 reported by Gregory Elkinbard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
MOS Ceilometer

Bug Description

In this environment Controllers and Mongo nodes are on separate compute elements (VMs for appliance).
If the controllers are started before the mongo nodes come online. Ceilometer backend may hang and not recover.

It should be possible to adjust the pacemaker dependencies list to wait until mongo is operational and then start ceilometer.
Rather then to force the user to do this by hand.

Tags: area-mos
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

I think, this should be fixed in Ceilometer code with connection timeouts for Mongo.

tags: added: area-library
Changed in fuel:
assignee: nobody → MOS Puppet Team (mos-puppet)
importance: Undecided → High
status: New → Confirmed
milestone: none → 8.0-updates
Changed in fuel:
assignee: MOS Puppet Team (mos-puppet) → MOS Ceilometer (mos-ceilometer)
milestone: 8.0-updates → 8.0
tags: added: area-mos
removed: area-library
Revision history for this message
Igor Degtiarov (idegtiarov) wrote :

Actually database reconnection already implemented and could be configured in ceilometer.conf file in [database] group.

Two parameter could be set there:
* times of reconnection attempts --- `max_retries` default value is 10 and
* timestamp between reconnection attempts --- `retry_interval` (10 sec by default).

Bug should be set to invalid.

Vitaly Gusev (vgusev)
Changed in fuel:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.