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

Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2006/08/08 11:08:23 UTC

[jira] Created: (AMQ-869) provide a broker-to-broker synchronization protocol so that an old master can be brought back online and synchronize up with a slave (which is running as a master) or to bring an old slave back online

provide a broker-to-broker synchronization protocol so that an old master can be brought back online and synchronize up with a slave (which is running as a master) or to bring an old slave back online
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: AMQ-869
                 URL: https://issues.apache.org/activemq/browse/AMQ-869
             Project: ActiveMQ
          Issue Type: New Feature
          Components: Broker
            Reporter: james strachan


We basically need 2 brokers to compare their current state and ensure they are both in exactly the same state.

e.g.

* both brokers checkpoint
* they perform a database merge
* they can now continue being a master-slave pair

Maybe the easiest implementation is to find the list of all unique message producers then perform a 'sequence-range' comparison.

e.g.

broker1:
producer1: 1-100, 102-142, 145
...

broker2:
producer1: 1-12

then we send from broker1 to broker2 producer1: 13-100, 102-142, 145


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira