activemq-dev mailing list archives

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

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

Gary Tully commented on AMQ-4165:
---------------------------------

Going forward, having journal replication and staged index updates is a better design. 
There is no intention to drop the HA ball.

Some experimental work on journal replication is ongoing and hardening will continue:
http://activemq.apache.org/kahadb-master-slave.html
https://github.com/fusesource/fuse-extra/tree/master/fusemq-leveldb (now at apache)
                
> 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

Mime
View raw message