[
https://issues.apache.org/jira/browse/AMQ-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-3376.
-----------------------------
Resolution: Won't Fix
Pure master slave functionality is removed in v5.8.0
> Master/slave + cluster leaves messages on slave
> -----------------------------------------------
>
> Key: AMQ-3376
> URL: https://issues.apache.org/jira/browse/AMQ-3376
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, Message Store
> Affects Versions: 5.5.0
> Environment: OS: Gentoo Linux.
> AMQ: apache-activemq-5.5.0-bin.tar.gz downloaded from
> http://activemq.apache.org/
> Reporter: Eivind Sivertsen
>
> I've setup 4 servers: two master/slave pairs, where the masters are
> clustered. Topology looks like this:
> !http://activemq.2283324.n4.nabble.com/file/n3617053/amq_setup.001.jpg!
> All nodes run on the same host, but within separate folders on the
> filesystem, so no nodes are sharing anything.
> I set up consumers on Node 1 and Node 3.
> I start producing messages to Node 1.
> Messages are distributed (load balanced) across Node 1 and Node 3 as
> expected, so consumers on both nodes receive messages.
> Messages produced to Node 1 are written to the slave node, Node 2, as
> expected. But messages that are forwarded to Node 3 for consumption there,
> are not deleted from Node 2.
> If I produce 1000 messages to Node 1, and 400 of those are forwarded to Node
> 3, there are 400 messages left on Node 2 when all messages are consumed from
> Node 1 and Node 3 (queueSize = 0 on both). So the messages that are consumed
> on Node 1 are deleted from Node 2, but not those forwarded to Node 3.
> A possible fix: messages that are received on a master node, but forwarded to
> another node in the cluster, are *not* stored on the slave node.
> The [ActiveMQ User mail list
> discussion|http://activemq.2283324.n4.nabble.com/Master-slave-cluster-leaves-messages-on-slave-td3617053.html]
> has links to the configurations for node 1-4.
--
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
