[
https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441355#comment-16441355
]
Justin Bertram commented on ARTEMIS-1285:
-----------------------------------------
bq. Seems to affect 2.5.0 also.
This issue was first reported against 2.1.0 and it hasn't been fixed so it's
not surprising it impacts 2.5.0 as well. "Spin-offs" are not really relevant
here.
bq. Most deployments will prefer an 3x data replication (1 live + 2x backup).
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." It's also
worth noting that the data is not actually replicated to the additional backup
until the live dies. At this point the current backup becomes live and the
additional backup then becomes its backup and it begins receiving the
replicated data. In other words, a live server only replicates to a single
backup at a time. Additional backups are simple idle. Up-to-date data only ever
exists in 2 places.
bq. Any hints on how we can help? What to look at?
Look at {{org.apache.activemq.artemis.core.server.impl.Activation}} and its
sub-classes (e.g.
{{org.apache.activemq.artemis.core.server.impl.SharedNothingBackupActivation}}).
They control the broker start-up and backup coordination.
> 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)
