Comment 3 for bug 1496386

This is as designed. We have rabbitmq running and it tells us that we are part of the same cluster as the node that is marked as rabbitmq "master" node.

Eternal restart of rabbitmq with fails may happen because of lack of memory or high cpu load that may lead to timeout. I would suggest setting this variable before you impose load on the cluster