Description of problem: We're missing step by step guide how to configure HornetQ in dedicated/colocated topology with shared store and message replication for EAP 6. Additional information: http://docs.jboss.org/hornetq/2.3.0.CR1/docs/user-manual/html_single/index.html
Created attachment 803408 [details] example_repl_collocated_ha_conf.zip Example configuration for HA with collocated backup and replicated journal.
There is new attribute max-saved-replicated-journal-size attribute which sets "The maximum number of backup journals to keep after failback occurs." This related only to replicated backup and should be in section: http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6.2/html/Administration_and_Configuration_Guide/Configuring_the_HornetQ_Servers_for_Replication.html which should be also replaced by more clear info with examples.
Hi Nidhi, configuration of message replication is well covered at this moment. What is still missing in documentation is some information about HA topologies and better description of configuration of shared store so: 1. In first HA chapter we should explain what is dedicated and collocated HA topology. 2. Then in the next chapter we're missing attributes for configuration HornetQ with shared store. Let me dive into this as I can see we're missing quite relevant info in EAP 5 HornetQ User Guide and community HornetQ documentation. ad 1.) to chapter 18.10.1. High Availability Introduction should be added There are 2 types of HA topologies: a) dedicated - there are 2 EAP 6 servers. In first is HornetQ configured as live, in second HornetQ configured as backup. In this topology EAP server with HornetQ configured as backup is just a container for HornetQ. It's inactive and cannot host any deployments like EJBs, MDBs or Servlets. b) collocated - there are 2 EAP servers where each contains 2 HornetQ servers. Those two EAP servers contains two live backup pairs. Where first live backup pair is formed by HornetQ live server on first EAP server and backup on second EAP server. Second live backup pair is formed by HornetQ live server on second EAP server and backup on first EAP server. (some simple diagram would for 1000 words) b) To configure the live and backup servers in dedicated topology with shared store, configure the standalone-X.xml files on each server to have the following: <shared-store>true</shared-store> <paging-directory path="${shared.directory}/journal"/> <bindings-directory path="${shared.directory}/bindings"/> <journal-directory path="${shared.directory}/journal"/> <large-messages-directory path="${shared.directory}/large-messages"/> ... <cluster-connections> <cluster-connection name="my-cluster"> ... </cluster-connection> </cluster-connections> Atributes for both server: failover-on-shutdown - Whether this server activates when when live or current active backup server is shut downed. paging-directory, bindings-directory, journal-directory, large-messages-directory contains path to shared store which in GFS2 or NFS and is the same for live and backup The backup server must also be flagged explicitly as a backup. <backup>true</backup> Attributes for backup server: allow-failback - Whether this server will automatically shutdown if the original live server comes back up. One more thing. In docbuilder I can see chapter for HornetQ core bridges and JMS bridges in HA chapter. Can you put them away from this chapter. Thanks, Mirek
Thanks Nidhi! Changes are looking great! If there is need to go deeper in this then we'll solve it in other BZs.
*** Bug 980078 has been marked as a duplicate of this bug. ***