Description
Pure master/slave was introduced over 7 years ago a means of getting a tick box for high availability. It is severely limited, in that only one slave is supported, a slave must be running before the master and no attempt is made at synchronising a new slave.
Unfortunately, pure master/slave is sometimes used as an option by ActiveMQ users, unaware of the dangers of doing so, at extreme risk to themselves and others.
Pure master/slave is the spawn of hell and should be removed forthwith.
Attachments
Issue Links
- supercedes
-
AMQ-4150 in pure master/slave, when the network is not stable, neither master nor slave can provide service to client
-
- Resolved
-