Uploaded image for project: 'MCollective'
  1. MCollective
  2. MCO-104

using ActiveMQ, node re-subscribe breaks direct addressing

    XMLWordPrintable

Details

    • Bug
    • Status: Open
    • Normal
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      When a node does not cleanly shut down mcollective (due to host crash, hard reset, or in my case a simple reboot) and then comes back, activemq does not unsubscribe the original subscriber. It continues to attempt to send messages to both subscribers, which both have the same server identity, even though the dead one never answers and ICMP "Destination unreachable" packets come back instead. This isn't a problem with standard broadcast requests, but it is a problem when using direct addressing. In this case, the message goes into a queue and is only sent to one subscriber, and each time I've tried this it's been the dead subscriber, never the live one. So direct-addressed queries never get a response.

      The only way I can see to resolve this situation when it occurs is to restart ActiveMQ, which seems excessively disruptive (and anyway, you have to know you need to do this). If there's already some configuration setting to have the new subscriber displace the old one, I'd be happy to know what it is; otherwise, could MCollective implement this? It seems like the ActiveMQ concept of "durable subscribers" might be relevant.

      I'm using:
      RHEL 6
      ActiveMQ 5.8.0
      MCollective 2.2.3 on ruby 1.9.3

      Some more detailed background:
      https://bugzilla.redhat.com/show_bug.cgi?id=1028382
      http://stackoverflow.com/questions/20362334/how-can-mcollective-replace-a-dead-subscriber-from-an-activemq-queue

      Attachments

        Activity

          People

            Unassigned Unassigned
            redmine.exporter redmine.exporter
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Zendesk Support