You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2012/11/09 09:04:11 UTC
[jira] [Created] (AMQ-4165) Remove pure master/slave functionality
Rob Davies created AMQ-4165:
-------------------------------
Summary: 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
[jira] [Commented] (AMQ-4165) Remove pure master/slave
functionality
Posted by "Martin Serrano (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (AMQ-4165) Remove pure master/slave functionality
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-4165.
-------------------------------
Resolution: Fixed
Removed the pure master slave unit tests that were failing to build due to these code changes.
> 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
[jira] [Reopened] (AMQ-4165) Remove pure master/slave functionality
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish reopened AMQ-4165:
-------------------------------
While the functionality has been removed there are some tests for this that are still part of the build and cause build failures in activemq-core, notably:
activemq-core/src/test/java/org/apache/activemq/advisory/MasterSlaveTempQueueMemoryTest.java
activemq-core/src/test/java/org/apache/activemq/broker/ft/MasterSlaveSlaveDieTest.java
activemq-core/src/test/java/org/apache/activemq/broker/ft/MasterSlaveSlaveShutdownTest.java
activemq-core/src/test/java/org/apache/activemq/broker/ft/MasterSlaveProducerFlowControlTest.java
activemq-core/src/test/java/org/apache/activemq/broker/ft/TransactedTopicMasterSlaveTest.java
activemq-core/src/test/java/org/apache/activemq/bugs/AMQ2102Test.java
activemq-core/src/test/java/org/apache/activemq/bugs/AMQ2183Test.java
These should probably be removed as well. Its possible there are other broken tests that use XML configs, not sure though.
> 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
[jira] [Resolved] (AMQ-4165) Remove pure master/slave functionality
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-4165.
-----------------------------
Resolution: Fixed
Resolved by SVN revision 1408651
> 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