summaryrefslogtreecommitdiff
path: root/packaging/debs
diff options
context:
space:
mode:
authorAlexandru Scvortov <alexandru@rabbitmq.com>2011-01-31 10:59:45 +0000
committerAlexandru Scvortov <alexandru@rabbitmq.com>2011-01-31 10:59:45 +0000
commit68a0b3b3e3d72c537651ed0684f886a3def9ec5c (patch)
treea5b8aeb3929d58da314620629f655003a9a32de6 /packaging/debs
parentcc0fc355a4fc589e3da4bd1b8ede8148f216bfd4 (diff)
downloadrabbitmq-server-git-68a0b3b3e3d72c537651ed0684f886a3def9ec5c.tar.gz
monitor rabbits on clustered nodes
When a rabbit starts, it, * informs every other running node in the cluster that it has started, and * registers every other running node in the cluster as running. This should handle every possible case of nodes joining clusters, since every join should be followed by that node starting. We can't just monitor 'rabbit' on node ups, since those come in when mnesia joins the cluster. The rabbit process starts up a bit later.
Diffstat (limited to 'packaging/debs')
0 files changed, 0 insertions, 0 deletions