You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Dmitry Smeliansky (JIRA)" <ji...@apache.org> on 2018/11/07 16:54:00 UTC
[jira] [Updated] (ARTEMIS-2165) Not having backup available after
restart in colocated configuration
[ https://issues.apache.org/jira/browse/ARTEMIS-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitry Smeliansky updated ARTEMIS-2165:
---------------------------------------
Description:
We use colocated HA-policy and trying to achieve the following:
# We have 2 servers and wont reach one of them will hold a) 1 master b) 1 slave for the master of each other
# When we start the servers we have the above as we wonted
# When one of the server is going down, the slave on the second becomes a live master - till now everything is ok
# When the second server (which was down in step 3) is up, the slave from server 1 remains a live master and a slave for master 1 is not created in server 2.
All we want is : how the system should be configured, so after the step 4 we will have the exact topology as after the step 1.
# Start server 1 and server 2: server 1 has 1 master and 1 slave, server 2 has one master and one slave
# Restart server 2: server 1 has one master and one slave, server 2 has one master and one slave
This issue was asked multiple times in stackoverflow, but was never answered.
When using a co-located HA policy, the backups, maintained by some node are not restored after this node is restarted (not on this node and not on any other).
[https://stackoverflow.com/questions/52839706/artemis-2-6-0-colocated-ha-issues]
[https://stackoverflow.com/questions/52000662/artemis-colocated-ha-policy]
Our configuration was as the following:
{code:java}
<ha-policy>
<replication>
<colocated>
<backup-port-offset>100</backup-port-offset>
<request-backup>true</request-backup>
<max-backups>2</max-backups>
<backup-request-retries>-1</backup-request-retries>
<backup-request-retry-interval>5000</backup-request-retry-interval>
<master/>
<slave/>
</colocated>
</replication>
</ha-policy>{code}
Thanks
was:
This issue was asked multiple times in stackoverflow, but was never answered.
When using a co-located HA policy, the backups, maintained by some node are not restored after this node is restarted (not on this node and not on any other).
[https://stackoverflow.com/questions/52839706/artemis-2-6-0-colocated-ha-issues]
[https://stackoverflow.com/questions/52000662/artemis-colocated-ha-policy]
Our configuration was as the following:
{code:java}
<ha-policy>
<replication>
<colocated>
<backup-port-offset>100</backup-port-offset>
<request-backup>true</request-backup>
<max-backups>2</max-backups>
<backup-request-retries>-1</backup-request-retries>
<backup-request-retry-interval>5000</backup-request-retry-interval>
<master/>
<slave/>
</colocated>
</replication>
</ha-policy>{code}
Thanks
> Not having backup available after restart in colocated configuration
> --------------------------------------------------------------------
>
> Key: ARTEMIS-2165
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2165
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.6.0
> Reporter: Dmitry Smeliansky
> Priority: Major
>
> We use colocated HA-policy and trying to achieve the following:
> # We have 2 servers and wont reach one of them will hold a) 1 master b) 1 slave for the master of each other
> # When we start the servers we have the above as we wonted
> # When one of the server is going down, the slave on the second becomes a live master - till now everything is ok
> # When the second server (which was down in step 3) is up, the slave from server 1 remains a live master and a slave for master 1 is not created in server 2.
> All we want is : how the system should be configured, so after the step 4 we will have the exact topology as after the step 1.
> # Start server 1 and server 2: server 1 has 1 master and 1 slave, server 2 has one master and one slave
> # Restart server 2: server 1 has one master and one slave, server 2 has one master and one slave
>
> This issue was asked multiple times in stackoverflow, but was never answered.
> When using a co-located HA policy, the backups, maintained by some node are not restored after this node is restarted (not on this node and not on any other).
> [https://stackoverflow.com/questions/52839706/artemis-2-6-0-colocated-ha-issues]
> [https://stackoverflow.com/questions/52000662/artemis-colocated-ha-policy]
> Our configuration was as the following:
> {code:java}
> <ha-policy>
> <replication>
> <colocated>
> <backup-port-offset>100</backup-port-offset>
> <request-backup>true</request-backup>
> <max-backups>2</max-backups>
> <backup-request-retries>-1</backup-request-retries>
> <backup-request-retry-interval>5000</backup-request-retry-interval>
> <master/>
> <slave/>
> </colocated>
> </replication>
> </ha-policy>{code}
> Thanks
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)