Suggestions for maintaining a standalone configuration file for a cluster of multiple co-located live-backup nodes

Solution Verified - Updated -

Issue

  • We have 4 co-located live-backup nodes in the HornetQ cluster with one backup on each live node. For the deployment/setup of this in different environment we currently just maintain one standalone-full-ha.xml with all the cluster connectors and socket bindings defined. And replace the node names of live and backup for each node where necessary.

  • However, this would work fine as long as we have only 4 nodes. But when we plan to either add/remove the nodes from the cluster we would have to change in all the node's standalone configuration file. We are looking for suggestions on a better cleaner strategy which would help in quick alteration as per the scalability need.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.