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 2015/10/20 21:02:27 UTC

[jira] [Resolved] (ARTEMIS-256) Orchestrate fail-back deterministically

     [ https://issues.apache.org/jira/browse/ARTEMIS-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-256.
------------------------------------
    Resolution: Fixed

> Orchestrate fail-back deterministically
> ---------------------------------------
>
>                 Key: ARTEMIS-256
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-256
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>             Fix For: 1.1.1
>
>
> Currently fail-back using replication relies on a simple delay (i.e. failback-delay) to determine when the live broker has synchronized all its data to the backup broker (which will become the new live broker once fail-back completes). However, if failback-delay is too short then synchronization won't complete and both the live and backup brokers will be nonfunctional.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)