[
https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442018#comment-16442018
]
Denis Volkov commented on ARTEMIS-1285:
---------------------------------------
> because when the connection between the live and active backup fails the
> passive backup will not participate in the quorum voting.
Yes, because right now passive backup knows nothing about live (according to
this issue). But as the issue would be fixed (I hope) sooner or later the logic
behind voting may be changed also (at least I hope so :) )
And also maybe it's worth documenting this fact to save some time for others
who would want to make such deployment
> Most deployments don't even use HA
I'm sure it's true. Maybe original quote should've been like 'most HA
deployments without shared storage'. But that would be far less convincing :)
> 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)
