* Rabbitmq-server has 2 configuration settings that affect how long it will wait for the mnesia database to become available
* The default is 30 seconds x 10 retries = 300 seconds
* The startup wrapper rabbitmq-server-wait will wait only 10 seconds
* If the database does not come online within 10 seconds the startup script will fail despite the fact that rabbitmq-server is still waiting for another 290 seconds.
* This behavior leads to falsely identified failures in OpenStack for example when a Rabbitmq cluster is restarted out of order (LP: #1828988)
[Test Case]
* Create Rabbitmq cluster and create a queue with "ha-mode: all" policy
* Shut down nodes one by one
* Restart the node that was shut down first
* This node will fail to start because it was not the master of the queue
* Note that the startup script (SysV or systemd) will fail after 10 seconds while the rabbitmq-server process is still waiting for the database to come online
[Impact]
* Rabbitmq-server has 2 configuration settings that affect how long it will wait for the mnesia database to become available server- wait will wait only 10 seconds
* The default is 30 seconds x 10 retries = 300 seconds
* The startup wrapper rabbitmq-
* If the database does not come online within 10 seconds the startup script will fail despite the fact that rabbitmq-server is still waiting for another 290 seconds.
* This behavior leads to falsely identified failures in OpenStack for example when a Rabbitmq cluster is restarted out of order (LP: #1828988)
[Test Case]
* Create Rabbitmq cluster and create a queue with "ha-mode: all" policy
* Shut down nodes one by one
* Restart the node that was shut down first
* This node will fail to start because it was not the master of the queue
* Note that the startup script (SysV or systemd) will fail after 10 seconds while the rabbitmq-server process is still waiting for the database to come online
[Regression Potential]
* I am not aware of any potential regressions