Currently autoheal functionality is a subset of OCF script
functionality (autoheal is concerned only with network partitions, OCF
also handles all sort of cases where rabbitmq becomes stuck). But as
both of this functions cause stopping and starting of rabbits, it
results in unwanted interference - as we've observed in 1585128, where
it triggered bug in autoheal code.
Even if rabbitmq bug will be fixed, it makes no sense to use both
autoheal and OCF script (actually, when clustered rabbit will stop
getting stuck during network split, autoheal will be as good as OCF
script).
Reviewed: https:/ /review. openstack. org/322269 /git.openstack. org/cgit/ openstack/ fuel-library/ commit/ ?id=9e8834489e6 caec1b7e640ae56 d2fbf4bf2e3775
Committed: https:/
Submitter: Jenkins
Branch: master
commit 9e8834489e6caec 1b7e640ae56d2fb f4bf2e3775
Author: Alexey Lebedeff <email address hidden>
Date: Fri May 27 19:47:12 2016 +0300
Disable rabbitmq cluster partition handling
Currently autoheal functionality is a subset of OCF script
functionality (autoheal is concerned only with network partitions, OCF
also handles all sort of cases where rabbitmq becomes stuck). But as
both of this functions cause stopping and starting of rabbits, it
results in unwanted interference - as we've observed in 1585128, where
it triggered bug in autoheal code.
Even if rabbitmq bug will be fixed, it makes no sense to use both
autoheal and OCF script (actually, when clustered rabbit will stop
getting stuck during network split, autoheal will be as good as OCF
script).
Change-Id: I38fbf6d50e9aed 35f3c5e3bc1e17d e7001304706
Closes-Bug: 1585128