[
https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095960#comment-16095960
]
yangwei commented on ARTEMIS-1285:
----------------------------------
Hi, Justin Bertram,Thanks for the reply. The example succeeds.
In the example, we kill the current live server not the slave, right? But In
our case, we kill slave and expect the standby slave become the slave.
We use static connectors instead of discovery group, something like this:
<cluster-connection name="my-cluster">
<address>#</address>
<connector-ref>artemis-inner</connector-ref>
<message-load-balancing>STRICT</message-load-balancing>
<max-hops>1</max-hops>
<static-connectors>
<connector-ref>neighbor-inner</connector-ref>
<connector-ref>neighbor1-inner</connector-ref>
</static-connectors>
</cluster-connection>
> 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
>
> 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
(v6.4.14#64029)
