You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/11/07 13:39:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16678231#comment-16678231 ]
Justin Bertram commented on ARTEMIS-2165:
-----------------------------------------
[~dmitrysm2000], instead of linking to Stack Overflow please put a full description of the issue in the issue {{Description}} including steps to reproduce.
> 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
>
> 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)