Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2279

failover transport and rebalanceClusterClients=true should fall back to original broker list if no broker on updated cluster information is available.

XMLWordPrintable

    • +
    • Hide

      A workaround is to not use rebalanceClusterClients and updateClusterClients.
      However this can lead to an unfair distribution of clients across brokers in a cluster in particular cluster environments.
      E.g. in a cluster of two master/slave broker pairs where master brokerA is shut down, all clients will reconnect to the second master brokerB even before the slaveA broker has become the new masterA broker. If clients use long-lived connections - as recommended - they will all remain connected to master brokerB and no further load balancing will happen.

      Show
      A workaround is to not use rebalanceClusterClients and updateClusterClients . However this can lead to an unfair distribution of clients across brokers in a cluster in particular cluster environments. E.g. in a cluster of two master/slave broker pairs where master brokerA is shut down, all clients will reconnect to the second master brokerB even before the slaveA broker has become the new masterA broker. If clients use long-lived connections - as recommended - they will all remain connected to master brokerB and no further load balancing will happen.

      When using a broker configuration with rebalanceClusterClients=true and updateClusterClients=true, the client side failover transport should fall back to the original broker list (as specified in the failover: transport URL) if it fails to connect to any of the broker URLs it received as part of the broker cluster update.

      Currently the failover transport only tries to reconnect to those broker URLs that it received as part of a cluster update (ConnectionControl message) from the connected broker.

              gtully@redhat.com Gary Tully
              rhn-support-tmielke Torsten Mielke
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: