An ability to forcefully kick rabbitmq node from the cluster when it dies
Bug #1437348 reported by
Bogdan Dobrelya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Bogdan Dobrelya | ||
5.1.x |
Won't Fix
|
Undecided
|
Unassigned | ||
6.0.x |
Won't Fix
|
Undecided
|
Unassigned | ||
6.1.x |
Fix Committed
|
High
|
Bogdan Dobrelya |
Bug Description
Then the corosync node dies, the instances of clones running at the other corosync nodes do not receive a notification. That introduces for OCF RA logic an additional time lag to react and initiate the failover procedure, which is to reassemble the rabbit cluster w/o the failed node.
The solution is to provide a dedicated fencing system daemon running on the corosync nodes. This daemon should react on the dbus events triggered by the corosync-notifyd when corosync nodes leaving the cluster. The reaction should be to kick the dead rabbit node from the cluster.
Changed in fuel: | |
importance: | Undecided → High |
assignee: | nobody → Bogdan Dobrelya (bogdando) |
milestone: | none → 6.1 |
status: | New → In Progress |
Changed in fuel: | |
status: | Won't Fix → In Progress |
tags: | added: to-be-covered-by-tests |
To post a comment you must log in.
Addressed by https:/ /review. openstack. org/#/c/ 108792/