Table of Contents
- 13.1. General Introduction
- 13.2. HA offerings of the Java Broker
- 13.3. Two Node Cluster
- 13.4. Multi Node Cluster
- 13.5. Configuring a Virtual Host to be a node
- 13.6. Durability Guarantees
- 13.7. Client failover configuration
- 13.8. Qpid JMX API for HA
- 13.9. Monitoring cluster
- 13.10. Disk space requirements
- 13.11. Network Requirements
- 13.12. Security
- 13.13. Backups
- 13.14. Migration of a non-HA store to HA
- 13.15. Disaster Recovery
- 13.16. Performance
The term High Availability (HA) usually refers to having a number of instances of a service such as a Message Broker available so that should a service unexpectedly fail, or requires to be shutdown for maintenance, users may quickly connect to another instance and continue their work with minimal interuption. HA is one way to make a overall system more resilient by eliminating a single point of failure from a system.
HA offerings are usually categorised as Active/Active or Active/Passive. An Active/Active system is one where all nodes within the cluster are usuaully available for use by clients all of the time. In an Active/Passive system, one only node within the cluster is available for use by clients at any one time, whilst the others are in some kind of standby state, awaiting to quickly step-in in the event the active node becomes unavailable.