[
https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441463#comment-16441463
]
Denis Volkov commented on ARTEMIS-1285:
---------------------------------------
> 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.
The original issue was about killing current slave (node2). This makes the hole
between master (node1) and standby slave (node3) - node3 and node1 know nothing
about each other. And as a result they can't communicate with each other and
can't pass master role
Your 'replicated-multiple-failover' works if we kill nodes in 'good order' - we
kill node1 (which makes node2 new master and node3 new slave) and then node2
(making node3 new master).
But if we kill node2 and then node1, node3 would not know that it should
connect to node1, it will still wait for node2. And if we kill node1 after
that, we would have only node3 in standby slave mode.
> In my experience I'd say this is fairly uncommon. I do think it fits certain
> use-cases, but I wouldn't categorize this as "most deployments.
Also I can't agree with this one. 3-nodes deployment is quite common. The most
useful case (at least for me) is to avoid split-brains when 2 nodes think they
are masters.
> 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)
