Red Hat Bugzilla – Bug 1267172
[GSS](6.4.z) Rebalance RA Connections after new cluster nodes
Last modified: 2017-01-17 06:47:57 EST
HornetQ RA should be able to connect to new cluster members when they join a HornetQ cluster. At the moment, when a HornetQ RA which is configured with two static connectors pointing at remote HornetQ cluster, is started it will connect all its connection only to nodes that are running in the remote cluster. If there are nodes that join the remote cluster later, the RA will never connect to them.
It should be possible for the RA the change in cluster topology when new members are joining and rebalance its connections in such way that they are evenly spread among all cluster members.
When rebalancing is being performed, RA should allow for _graceful_ shutdown of existing connections that is any outstanding transactions should be allow to complete.
RA should provide an option for _hard_ shutdown if transactions do not complete within specified time out (configurable)
Step to reproduce:
Create a two node HornetQ cluster (JMSProvider-cluster) with a testQueue.
Create a two node HornetQ cluster (ApplicationProvider-cluster)
Configure HornetQ-Remote RA that points at JMSProvider-cluster.
Deploy MDB on ApplicationProvider-cluster that listens on remote testQueue in JMSProvider-cluster and uses HornetQ-Remote RA
Start node one in JMSProvider-cluster. After the node is started it should be possible to see in all connections for HornetQ-Remote RA have been allocated to that node for testQueue.
Start second node in JMSProvider-cluster. After the node is started it is possible to see that there are no connections on that node for HornetQ-Remote RA on testQueue.
Justin Bertram <firstname.lastname@example.org> updated the status of jira HORNETQ-1495 to Resolved
Setting as verified with EAP 6.4.6.CP.CR2.
*** Bug 1261984 has been marked as a duplicate of this bug. ***
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.