Openstack HA , rabbitmq cluster in partition state after isolation of data/control interface
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.0 |
Fix Committed
|
High
|
venu kolli | |||
Trunk |
Fix Committed
|
High
|
venu kolli |
Bug Description
Rabbitmq cluster in partition state after isolation of data/control interface.
Issue observed on R2.0 build 12 with Sanju's fixes.
After isolating data/control interface on node 1 and bring the interface back , rabbit cluster is still in partition state.
root@vse2100-
Cluster status of node 'rabbit@
[{nodes,
[{disc,
{running_nodes,
['
'
{partitions,
[{
...done.
root@vse2100-
root@vse2100-
tags: | added: ha |
Changed in juniperopenstack: | |
importance: | Undecided → High |
assignee: | nobody → Sanju Abraham (asanju) |
information type: | Proprietary → Public |
The fix addresses the issue of rabbitmq cluster partitioned on interface and link failures. In such cases, with autoheal flag does not fully recover. As per the documentation from rabbitmq, some of the fixes around recovery for autoheal is done in 3.3.0 and till that time the only way the partition can be restored is to restart rabbit on the node where is has the latest transaction ID