[
https://issues.apache.org/jira/browse/ARTEMIS-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-2128.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.10.0
I just tested with with 2.10.0-SNAPSHOT and the 2nd backup attached to the live
once the 1st backup once killed.
> Replication - 2nd backup server is unable to go into passive mode
> -----------------------------------------------------------------
>
> Key: ARTEMIS-2128
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2128
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.6.3
> Reporter: Pawel
> Priority: Major
> Fix For: 2.10.0
>
>
> I've created basic cluster containing master (master) and 2 backups (slave1,
> slave2). When I started cluster, the master is live, the slave1 is backup in
> passive mode, the slave2 is spare backup.
> If I shutdown master, everything is ok (slave1 becomes live and slave2
> becomes passive backup).
> But when I shoutdown slave1 first (master is still live), slave2 is unable to
> go into passive mode (so there are no backup ready to become live).
> Example config:
> master:
> {code:xml}
> ...
> <cluster-user>cluster-user</cluster-user>
> <cluster-password>cluster-password</cluster-password>
> <cluster-connections>
> <cluster-connection name="my-cluster">
> <connector-ref>netty-connector</connector-ref>
> <use-duplicate-detection>true</use-duplicate-detection>
> <static-connectors>
> <connector-ref>slave1</connector-ref>
> <connector-ref>slave2</connector-ref>
> </static-connectors>
> </cluster-connection>
> </cluster-connections>
> <ha-policy>
> <replication>
> <master>
> <check-for-live-server>true</check-for-live-server>
> <vote-on-replication-failure>true</vote-on-replication-failure>
> <group-name>internal-broker</group-name>
> <cluster-name>my-cluster</cluster-name>
> </master>
> </replication>
> </ha-policy>
> ...
> {code}
> slave1:
> {code:xml}
> ...
> <cluster-user>cluster-user</cluster-user>
> <cluster-password>cluster-password</cluster-password>
> <cluster-connections>
> <cluster-connection name="my-cluster">
> <connector-ref>netty-connector</connector-ref>
> <use-duplicate-detection>true</use-duplicate-detection>
> <static-connectors>
> <connector-ref>master</connector-ref>
> <connector-ref>slave2</connector-ref>
> </static-connectors>
> </cluster-connection>
> </cluster-connections>
> <ha-policy>
> <replication>
> <slave>
> <group-name>internal-broker</group-name>
> <cluster-name>my-cluster</cluster-name>
> <allow-failback>true</allow-failback>
> </slave>
> </replication>
> </ha-policy>
> ...
> {code}
> slave2:
>
> {code:xml}
> ...
> <cluster-user>cluster-user</cluster-user>
> <cluster-password>cluster-password</cluster-password>
> <cluster-connections>
> <cluster-connection name="my-cluster">
> <connector-ref>netty-connector</connector-ref>
> <use-duplicate-detection>true</use-duplicate-detection>
> <static-connectors>
> <connector-ref>master</connector-ref>
> <connector-ref>slave1</connector-ref>
> </static-connectors>
> </cluster-connection>
> </cluster-connections>
> <ha-policy>
> <replication>
> <slave>
> <group-name>internal-broker</group-name>
> <cluster-name>my-cluster</cluster-name>
> <allow-failback>true</allow-failback>
> </slave>
> </replication>
> </ha-policy>
> ...
> {code}
>
> And I've additional question: is it possible to create quorum based on only
> one live server in cluster, so 3 nodes (master, slave1, slave2) would be able
> to vote?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
