Uploaded image for project: 'AMQ Interconnect'
  1. AMQ Interconnect
  2. ENTMQIC-1992

Enabling AMQ 7.1 broker failback breaks failover support

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.2.0.CR2
    • 1.1.0.GA
    • None
    • Release Notes
    • +
    • Hide
      Previously, if a router was connected to the master instance of a broker cluster, and then failed over to the backup instance, it was possible for the router to lose track of the master instance and fail to reconnect to it once it was back online. This issue has been fixed to ensure that a router can always reconnect to the original master instance in a broker cluster.
      Show
      Previously, if a router was connected to the master instance of a broker cluster, and then failed over to the backup instance, it was possible for the router to lose track of the master instance and fail to reconnect to it once it was back online. This issue has been fixed to ensure that a router can always reconnect to the original master instance in a broker cluster.
    • Documented as Resolved Issue
    • Hide

      See attached configuration.

      • Start broker-master
      • Once broker-master is up start broker-slave
      • Start the router
      • Test sending and receiving and failoverList
      • Stop broker-master, backup slave should become live
      • Test sending and receiving and failoverList
      • Restart broker-master and allow it to become live and slave backup once again
      • Test sending and receiving and failoverList
      Show
      See attached configuration. Start broker-master Once broker-master is up start broker-slave Start the router Test sending and receiving and failoverList Stop broker-master, backup slave should become live Test sending and receiving and failoverList Restart broker-master and allow it to become live and slave backup once again Test sending and receiving and failoverList
    • Interconnect - June Sprint

    Description

      This may be a broker related problem, however from the end developer's perspective...

      Upon configuring two brokers for failover and a single router as per ENTMQIC-1975 I see that the router correctly fails over to the slave and sending messages is successful both before and after the single failover.
      Initial failover data:

      [0x2534010]:0 <- @open(16) [container-id="broker-master", max-frame-size=4294967295, channel-max=65535, idle-time-out=30000, offered-capabilities=@PN_SYMBOL[:"sole-connection-for-container", :"DELAYED_DELIVERY", :"SHARED-SUBS", :"ANONYMOUS
-RELAY"], properties={:product="apache-activemq-artemis", :"failover-server-list"=[{:hostname="192.168.2.208", :scheme="amqp", :port=62616, :"network-host"="192.168.2.208"}], :version="2.4.0.amq-710004-redhat-1"}]

      An an initial qdmanage query of the failoverList

      [rkieley@ic1rh configuration]$ qdmanage -b amqp://192.168.2.208:5672 --type=connector query failoverList                                                                                                                                       
[
  {
    "failoverList": "amqp://192.168.2.208:5672"
  }
]

      Both prior to failover and after I can send and receive messages via the live broker successfully.

      However when failover occurs I do not see any failover related information being received by the router and a subsequent check of the failoverList reveals:

      [rkieley@ic1rh configuration]$ qdmanage -b amqp://192.168.2.208:5672 --type=connector query failoverList
[]
[rkieley@ic1rh configuration]$

      Once failback occurs I can no longer successfully send messages via the waypointed address.

      Attachments

        Issue Links

          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. ENTMQIC-1920 Honor alternate URL provided by connected brokers

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQIC-1975 failover not working with master/slave Artemis brokers

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQIC-1994 When using linkRoute and AMQP client failover, connection is not reestablished if broker connection is lost

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-1763 Acceptor is available before HA replication with backup server is complete, causing fail-over-list to be empty

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              gmurthy@redhat.com Ganesh Murthy
              rhn-support-rkieley Roderick Kieley
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: