RabbitMQ cluster, controlled by pacemaker.
Our life with RabbitMQ cluster gave us following issues:
* RabbitMQ cluster can't assemble after reboot controllers (with probability close to 50%)
* When closter lost node, which responsible for the integrity of the cluster, cluster died.
This issues can't be resolved without external control. As the dictator's perfect Pacemaker. On its OCF-scripts we can realize any start/stop/checking logic.
Feature Lead: Sergey Vasilenko
Developers: Sergey Vasilenko
Mandatory Design Reviewers: Vladimir Kuklin
QA: Nastya Urlapova
Blueprint information
- Status:
- Complete
- Approver:
- Vladimir Kuklin
- Priority:
- High
- Drafter:
- Sergey Vasilenko
- Direction:
- Approved
- Assignee:
- Sergey Vasilenko
- Definition:
- Approved
- Series goal:
- Accepted for 5.1.x
- Implementation:
-
Implemented
- Milestone target:
-
5.1
- Started by
- Mike Scherbakov
- Completed by
- Vladimir Kuklin
Related branches
Related bugs
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Rabbitmq ocf master/slave
The flow charts http://
Work Items
Work items:
1-st stage blueprint: DONE
POC OCF script: DONE
Code review: DONE
QA: DONE
describing behavior and implementation details: DONE
implement partition checking as additional monitor task: TODO
Dependency tree
* Blueprints in grey have been implemented.
