[
https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441417#comment-16441417
]
Justin Bertram commented on ARTEMIS-1285:
-----------------------------------------
> The underlying problem is that on a fresh install of Artemis with live (r1)
> plus r2 (1st replica) and r3 (2nd replica) makes the "r3" instance go into
> that logging loop. So we can't even reach the situation of having the 1x live
> + 2 backups due to a bug (probably in locating the node).
Can you take a look at the "replicated-multiple-failover" example and tell me
how your use-case differs from that? It starts a master and 2 backups and then
triggers 2 failovers so that ultimately the 2nd backup is live and serving
messages. The example works on 2.5.0 which indicates this functionality is
working.
> Standby slave would not announce replication to master when the slave is down
> -----------------------------------------------------------------------------
>
> Key: ARTEMIS-1285
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1285
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.1.0
> Reporter: yangwei
> Priority: Major
>
> We have a cluster of 3 instances: A is master, B is slave and C is standby
> slave. When slave is down, we expect C announces replication to A but A is in
> standalone mode all the time. We see C waits at "nodeLocator.locateNode()"
> through jstack command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
