User should be able to choose RabbitMQ network partition policy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Medium
|
Radosław Piliszek | ||
Train |
Fix Released
|
Medium
|
Radosław Piliszek |
Bug Description
By defaut [1], the RabbitMQ network policy should not be set to autoheal
which could result to a split-brain but to pause_minority or even ignore.
With pause_minority, you get consistency while sacrificing availability.
The minority node(s) will pause and disconnect all clients. The clients
will reconnect to other nodes in the majority-half of the cluster and
resume normal operation.
With autoheal, you get availability while sacrificing consistency. The
cluster becomes "split-brained". The success of each RPC request is
contingent upon all participating connections involved in the request
being on the same partition as one another, which is not very likely.
So until the partition ends, the system will be in a degraded state and
most things are going to fail.
Source: [2]
User should be able to choose the policy by using an option in globals.yml
- [1] https:/
- [2] https:/
Changed in kolla-ansible: | |
assignee: | Gaëtan Trellu (goldyfruit) → Radosław Piliszek (yoctozepto) |
Changed in kolla-ansible: | |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. opendev. org/672562
Review: https:/