activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SL (JIRA)" <>
Subject [jira] [Commented] (AMQ-4165) Remove pure master/slave functionality
Date Fri, 07 Dec 2012 18:55:21 GMT


SL commented on AMQ-4165:

The functionnality provided by this mode had its issues
(such the one i stumbled upon )
But it was exposed as a valid option in the documentation until recently (and not completly
removed yet) ; cutting it like that is harsh. None of the few "alternatives" can handle the
same use cases, and are expecting a very different set of requirements (such as a database
or a shared filesystem).
Is there any plan to complete the amq options in this area or is the project dropping the
ball on HA ?

> 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