[jboss-jira] [JBoss JIRA] (WFLY-6654) Optimize live/backup replication after failback
[
https://issues.jboss.org/browse/WFLY-6654?page=com.atlassian.jira.plugin....
]
Clebert Suconic closed WFLY-6654.
---------------------------------
Resolution: Rejected
I wish it was this simple... I added a comment saying why it would be impossible/
difficult to do it.
You would need to find the deltas of what's needed, and even then it's impossible
to guarantee it's coming from the same journal.
You would need to invest a lot into something not worthy the investment.
Optimize live/backup replication after failback
-----------------------------------------------
Key: WFLY-6654
URL: https://issues.jboss.org/browse/WFLY-6654
Project: WildFly
Issue Type: Enhancement
Components: JMS
Affects Versions: 10.0.0.Final
Reporter: Miroslav Novak
Assignee: Clebert Suconic
Priority: Critical
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.4.11#64026)