partition coordinator with file driver didn't remove member after leaving group

Bug #1484466 reported by Liusheng
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceilometer
Invalid
Undecided
Liusheng
tooz
Invalid
Undecided
Liusheng

Bug Description

In devstack environment with mysql storage backend, following steps to reproduce this issue:

1. drop all db tables
2. do ceilometer-dbsync.
3. config the coordination backend_url as "backend_url=file:///opt/stack/partitioncoordinator/lock"
4. restart ceilometer services (include ceilometer-agent-notification and ceilometer-polling)

the "ceilometer meter-list" command will return a empty list.

when I restart agent-notification service with an separated config file without partition backend_url, it can works ok.

---------------------------------------------------------------

The main reason of above issue is because I have configured the backend_url of partition_coordinator as file driver. after restarting the ceilometer-polling service several times, the polling-agent cannot poll resources, because with file driver, the member of partition group will still exist even the member leaved after restarting service. the member of tooz partition with filter driver is show as a file, the file won't be removed after group member leaved.

Liusheng (liusheng)
Changed in ceilometer:
assignee: nobody → Liusheng (liusheng)
Revision history for this message
Liusheng (liusheng) wrote :

it seems something wrong related with the version of oslo.service, similar with bug 1484765, will dig more, change the status to incomplate

Changed in ceilometer:
status: New → Incomplete
Liusheng (liusheng)
description: updated
summary: - notification-agent cannot works with partition coordinator
+ partition coordinator with file driver didn't remove member after
+ leaving group
Changed in ceilometer:
status: Incomplete → Invalid
Changed in python-tooz:
assignee: nobody → Liusheng (liusheng)
Revision history for this message
Ben Nemec (bnemec) wrote :

Any update on this? It's not really clear what the status is based on the latest comments and status changes.

Changed in python-tooz:
status: New → Incomplete
Revision history for this message
Takashi Kajinami (kajinamit) wrote :

This has been inactive for long so I'll invalidate this.

Changed in python-tooz:
status: Incomplete → 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.