Hi everyone,
I am using Artemis 2.2.0 and HA with replication and three brokers: one
master and two slaves (the configuration extracts, named
master/slave1/slave2, are below).
Running the following scenario I am not sure if it is a bug or works as
designed:
1) start master
2) start slave1 (logging “…AMQ221031: backup announced”)
3) start slave2 (logging “…waiting live to fail before it gets active”)
4) kill slave1
The master recognize the failure and shows “AMQ222092: Connection to the
backup node failed, removing replication now” in his log. I would assume
slave2 to become automatically the backup of the master but it does nothing.
To manually solve this behavior I have tested two alternatives (without
restarting the master or having a downtime):
A) restart slave2 (yes, not slave1) and then it becomes the backup of the
master
B) restart slave1 and everything is as before the failure
Regarding A the current behavior seems to be a bug. Or is there any
configuration to set?
*Extract of master-config*
<ha-policy>
<replication>
<master>
<check-for-live-server>true</check-for-live-server>
</master>
</replication>
</ha-policy>
<connectors>
<connector name="netty-connector">tcp://192.168.0.10:61616</connector>
<connector
name="netty-backup-connector-slave1">tcp://192.168.0.11:61616</connector>
<connector
name="netty-backup-connector-slave2">tcp://192.168.0.12:61616</connector>
</connectors>
<acceptors>
<acceptor name="netty-acceptor">tcp://0.0.0.0:61616</acceptor>
</acceptors>
<cluster-connections>
<cluster-connection name="cluster">
<connector-ref>netty-connector</connector-ref>
<static-connectors allow-direct-connections-only="true">
<connector-ref>netty-backup-connector-slave1</connector-ref>
<connector-ref>netty-backup-connector-slave2</connector-ref>
</static-connectors>
</cluster-connection>
</cluster-connections>
*Extract of slave1-config*
<ha-policy>
<replication>
<slave>
<allow-failback>false</allow-failback>
</slave>
</replication>
</ha-policy>
<connectors>
<connector
name="netty-live-connector">tcp://192.168.0.10:61616</connector>
<connector name="netty-connector">tcp://192.168.0.11:61616</connector>
<connector
name="netty-backup-connector-slave2">tcp://192.168.0.12:61616</connector>
</connectors>
<acceptors>
<acceptor name="netty-acceptor">tcp://0.0.0.0:61616</acceptor>
</acceptors>
<cluster-connections>
<cluster-connection name="cluster">
<connector-ref>netty-connector</connector-ref>
<static-connectors allow-direct-connections-only="true">
<connector-ref>netty-live-connector</connector-ref>
<connector-ref>netty-backup-connector-slave2</connector-ref>
</static-connectors>
</cluster-connection>
</cluster-connections>
*Extract of slave2-config*
<ha-policy>
<replication>
<slave>
<allow-failback>false</allow-failback>
</slave>
</replication>
</ha-policy>
<connectors>
<connector
name="netty-live-connector">tcp://192.168.0.10:61616</connector>
<connector
name="netty-backup-connector-slave1">tcp://192.168.0.11:61616</connector>
<connector name="netty-connector">tcp://192.168.0.12:61616</connector>
</connectors>
<acceptors>
<acceptor name="netty-acceptor">tcp://0.0.0.0:61616</acceptor>
</acceptors>
<cluster-connections>
<cluster-connection name="cluster">
<connector-ref>netty-connector</connector-ref>
<static-connectors allow-direct-connections-only="true">
<connector-ref>netty-live-connector</connector-ref>
<connector-ref>netty-backup-connector-slave1</connector-ref>
</static-connectors>
</cluster-connection>
</cluster-connections>
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html