activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] [Commented] (AMQ-4165) Remove pure master/slave functionality
Date Fri, 12 Apr 2013 10:24:15 GMT


Gary Tully commented on AMQ-4165:

Here are some of the known limitations of pure master slave:
 - state replication at the openwire command level is too complex
 - use of a single master connection is a bottleneck
 - inability to catch up on state for a new slave after failover

> Remove pure master/slave functionality
> --------------------------------------
>                 Key: AMQ-4165
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.7.0
>            Reporter: Rob Davies
>            Assignee: Rob Davies
>             Fix For: 5.8.0
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message