You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Miroslav Novak (JIRA)" <ji...@apache.org> on 2016/05/26 12:00:17 UTC

[jira] [Created] (ARTEMIS-541) Optimize live/backup replication after failback

Miroslav Novak created ARTEMIS-541:
--------------------------------------

             Summary: Optimize live/backup replication after failback
                 Key: ARTEMIS-541
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-541
             Project: ActiveMQ Artemis
          Issue Type: Bug
          Components: Broker
    Affects Versions: 1.3.0
            Reporter: Miroslav Novak


Currently if there is master/slave pair configured using replicated journal then after each failback when master is starting, it copies the whole journal directory from slave.
This seems to ineffective as master might have significant part of backups journal before it failed. 

If only differences between journals would be transfered then it would be effective especially in case when failback is completed and master starts to synchronize the whole journal back to slave. It copies the whole journal to backup again which is almost the same. This would greatly speed up synchronization of slave and safe network bandwidth.



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