Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 29 Nov 2012 22:06:58 +0000 (UTC)
From: "Martin Serrano (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <707330665.42507.1354226818305.JavaMail.jiratomcat@arcas>
In-Reply-To: <1177592287.90674.1352448252097.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (AMQ-4165) Remove pure master/slave
 functionality
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506859#comment-13506859 ] 

Martin Serrano commented on AMQ-4165:
-------------------------------------

so what alternative is there when a SAN/shared disk is not available?
                
> Remove pure master/slave functionality
> --------------------------------------
>
>                 Key: AMQ-4165
>                 URL: https://issues.apache.org/jira/browse/AMQ-4165
>             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: http://www.atlassian.com/software/jira