Hi,


I have a cluster of 3 rabbits (version 2.7.1), and a bunch of services
that connect to it and declare a bunch of H/A queues. Some of the
queues are exclusive, some aren't.


Some of the services are connected to rabbit01 and some to rabbit03.
Nobody's connected to rabbit02.


Then I kill rabbit02, and, after a short while (but not immediately),
rabbitmqctl list_queues, rabbitmqctl list_connections and rabbitmqctl
list_channels completely stop working - they just hang.


After these start hanging, I killed all applications that were
connected to RabbitMQ, and then I killed rabbit03 so only rabbit01
remained. But those rabbitmqctl commands were still hanging. However,
if I restart rabbit01 and bring up the other cluster nodes, everything
is working again.


It seems like there was some internal error that lead to death of a
mirrored queue coordinator process, or something... I'm attaching the
log from rabbit01.


--
Eugene Kirpichov
http://www.linkedin.com/in/eugenekirpichov
We're hiring! http://tinyurl.com/mirantis-openstack-engineer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rabbit at control01.log
Type: application/octet-stream
Size: 24844 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121017/cb02d087/attachment.obj>

Search Discussions

  • Simon MacMullen at Oct 18, 2012 at 10:28 am

    On 17/10/12 22:41, Eugene Kirpichov wrote:
    It seems like there was some internal error that lead to death of a
    mirrored queue coordinator process, or something... I'm attaching the
    log from rabbit01.

    Thanks.


    That looks like a bug which has been substantially mitigated since
    2.7.1, although a complete fix for it will be in the next release.


    To be honest, we have fixed a lot of bugs in mirrored queues since 2.7.1
    - so I would strongly recommend an upgrade anyway.


    Cheers, Simon


    --
    Simon MacMullen
    RabbitMQ, VMware
  • Eugene Kirpichov at Oct 18, 2012 at 2:48 pm
    Thanks Simon! I'll try that with 2.8.7.

    On Thu, Oct 18, 2012 at 3:28 AM, Simon MacMullen wrote:
    On 17/10/12 22:41, Eugene Kirpichov wrote:

    It seems like there was some internal error that lead to death of a
    mirrored queue coordinator process, or something... I'm attaching the
    log from rabbit01.

    Thanks.

    That looks like a bug which has been substantially mitigated since 2.7.1,
    although a complete fix for it will be in the next release.

    To be honest, we have fixed a lot of bugs in mirrored queues since 2.7.1 -
    so I would strongly recommend an upgrade anyway.

    Cheers, Simon

    --
    Simon MacMullen
    RabbitMQ, VMware





    --
    Eugene Kirpichov
    http://www.linkedin.com/in/eugenekirpichov
    We're hiring! http://tinyurl.com/mirantis-openstack-engineer

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouprabbitmq-discuss @
categoriesrabbitmq
postedOct 17, '12 at 9:41p
activeOct 18, '12 at 2:48p
posts3
users2
websiterabbitmq.com
irc#rabbitmq

People

Translate

site design / logo © 2017 Grokbase