Had a node crashed in a cluster. All clients then reconnected, but the old
connections to the crashed node was still reported by the mgmt api.
Shouldn't connection stats for connections to a node which is down be
automatically cleared?






--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Connection-count-on-node-crash-tp28594.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

Search Discussions

  • Simon MacMullen at Aug 6, 2013 at 9:32 am

    On 06/08/13 08:08, carlhoerberg wrote:
    Had a node crashed in a cluster. All clients then reconnected, but the old
    connections to the crashed node was still reported by the mgmt api.
    Shouldn't connection stats for connections to a node which is down be
    automatically cleared?

    There was a bug to that effect fixed in 3.0.3. Are you running an older
    version?


    Cheers, Simon


    --
    Simon MacMullen
    RabbitMQ, Pivotal
  • Carlhoerberg at Aug 6, 2013 at 9:37 am
    This was a 3.0.3 and 3.0.4 server running in a cluster, it was the 3.0.4 node that crashed.






    On Tuesday 6 August 2013 at 11:34, Simon MacMullen-2 [via RabbitMQ] wrote:

    On 06/08/13 08:08, carlhoerberg wrote:
    Had a node crashed in a cluster. All clients then reconnected, but the old
    connections to the crashed node was still reported by the mgmt api.
    Shouldn't connection stats for connections to a node which is down be
    automatically cleared?

    There was a bug to that effect fixed in 3.0.3. Are you running an older
    version?

    Cheers, Simon

    --
    Simon MacMullen
    RabbitMQ, Pivotal
    _______________________________________________
    rabbitmq-discuss mailing list
    [hidden email] (/user/SendEmail.jtp?type=node&node(600&i=0)
    https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss


    If you reply to this email, your message will be added to the discussion below: http://rabbitmq.1065348.n5.nabble.com/Connection-count-on-node-crash-tp28594p28600.html
    To unsubscribe from Connection count on node crash, click here (http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node(594&code=Y2FybC5ob2VyYmVyZ0BnbWFpbC5jb218Mjg1OTR8LTEyNDcxMDc4NjM=).
    NAML (http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml)













    --
    View this message in context: http://rabbitmq.1065348.n5.nabble.com/Connection-count-on-node-crash-tp28594p28601.html
    Sent from the RabbitMQ mailing list archive at Nabble.com.
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130806/e7cf8938/attachment.htm>

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouprabbitmq-discuss @
categoriesrabbitmq
postedAug 6, '13 at 7:08a
activeAug 6, '13 at 9:37a
posts3
users2
websiterabbitmq.com
irc#rabbitmq

2 users in discussion

Carlhoerberg: 2 posts Simon MacMullen: 1 post

People

Translate

site design / logo © 2017 Grokbase