WildFly HornetQ Shared Filesystem-Based Collocated HA Configuration
External
- Collocated Live-Backup HornetQ setup in EAP 6 https://access.redhat.com/solutions/400873
Internal
Overview
This article describes the steps required to implement a highly available collocated HornetQ topology with EAP 6 and higher. The concepts behind such a topology are presented here:
For high availability purposes, the live server and the backup server instances must be installed on two separated physical (or virtual) hosts, provisioned in such a way to minimize the probability of both host failing at the same time. Highly available HornetQ requires access to reliable shared file system storage, so a file system such as GFS2 or a SAN must be made available to both hosts. HornetQ instances will store on the shared directory, among other things, their bindings and journal files. NFS v4 appropriately configured is also an option.
Procedure
<paths> <path name="hornetq.shared.dir.pair.A" path="/nfs/hornetq-shared-storage-pair-A"/> <path name="hornetq.shared.dir.pair.B" path="/nfs/hornetq-shared-storage-pair-B"/> </paths>
Node 1 Configuration
<subsystem xmlns="urn:jboss:domain:messaging:1.4"> <hornetq-server name="active-pair-A"> ... <backup>false</backup> <persistence-enabled>true</persistence-enabled> <shared-store>true</shared-store> <create-bindings-dir>true</create-bindings-dir> <create-journal-dir>true</create-journal-dir> <failover-on-shutdown>true</failover-on-shutdown> <paging-directory path="paging" relative-to="hornetq.shared.dir.pair.A"/> <bindings-directory path="bindings" relative-to="hornetq.shared.dir.pair.A"/> <journal-directory path="journal" relative-to="hornetq.shared.dir.pair.A"/> <large-messages-directory path="large-messages" relative-to="hornetq.shared.dir.pair.A"/> ... <jms-connection-factories> ... <connection-factory name="RemoteConnectionFactory"> <ha>true</ha> <retry-interval>1000</retry-interval> <retry-interval-multiplier>1.0</retry-interval-multiplier> <reconnect-attempts>-1</reconnect-attempts> <connectors> <connector-ref connector-name="netty"/> </connectors> <entries> <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/> </entries> </connection-factory> ... </jms-connection-factories> </hornetq-server> <hornetq-server name="standby-pair-B"> ... <backup>true</backup> <persistence-enabled>true</persistence-enabled> <shared-store>true</shared-store> <create-bindings-dir>true</create-bindings-dir> <create-journal-dir>true</create-journal-dir> <failover-on-shutdown>true</failover-on-shutdown> <paging-directory path="paging" relative-to="hornetq.shared.dir.pair.B"/> <bindings-directory path="bindings" relative-to="hornetq.shared.dir.pair.B"/> <journal-directory path="journal" relative-to="hornetq.shared.dir.pair.B"/> <large-messages-directory path="large-messages" relative-to="hornetq.shared.dir.pair.B"/> ... <!-- The <jms-connection-factories> section must be completely commented out. <jms-connection-factories> ... </jms-connection-factories> --> </hornetq-server> </subsystem>
JMS Connection Factories
A backup HornetQ instance does not need the <jms-connection-factories> and <jms-destinations> sections as any JMS components are created from the shared journal when the backup server becomes live.
Log Output
Active server starting:
13:14:00,312 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/nfs/hornetq-shared-storage/journal,bindingsDirectory=/nfs/hornetq-shared-storage/bindings,largeMessagesDirectory=/nfs/hornetq-shared-storage/large-messages,pagingDirectory=/nfs/hornetq-shared-storage/paging) 13:14:00,313 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221006: Waiting to obtain live lock [...] 13:14:00,614 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221035: Live Server Obtained live lock [...] 13:14:01,800 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221007: Server is now live 13:14:01,801 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221001: HornetQ Server version 2.3.25.Final (2.3.x, 123) [db446058-de41-11e5-aea0-174ba3e38330]
Stand-by server starting:
13:18:19,380 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221000: backup server is starting with configuration HornetQ Configuration (clustered=false,backup=true,sharedStore=true,journalDirectory=/nfs/hornetq-shared-storage/journal,bindingsDirectory=/nfs/hornetq-shared-storage/bindings,largeMessagesDirectory=/nfs/hornetq-shared-storage/large-messages,pagingDirectory=/nfs/hornetq-shared-storage/paging) 13:18:19,402 INFO [org.hornetq.core.server] (HQ119000: Activation for server HornetQServerImpl::serverUUID=db446058-de41-11e5-aea0-174ba3e38330) HQ221032: Waiting to become backup node 13:18:19,449 INFO [org.hornetq.core.server] (HQ119000: Activation for server HornetQServerImpl::serverUUID=db446058-de41-11e5-aea0-174ba3e38330) HQ221033: ** got backup lock [...] 13:18:19,680 INFO [org.hornetq.core.server] (HQ119000: Activation for server HornetQServerImpl::serverUUID=db446058-de41-11e5-aea0-174ba3e38330) HQ221109: HornetQ Backup Server version 2.3.25.Final (2.3.x, 123) [db446058-de41-11e5-aea0-174ba3e38330] started, waiting live to fail before it gets active root@h2#
Failover to stand-by server:
[...] 13:20:21,911 INFO [org.hornetq.core.server] (HQ119000: Activation for server HornetQServerImpl::serverUUID=db446058-de41-11e5-aea0-174ba3e38330) HQ221010: Backup Server is now live