[
https://issues.apache.org/activemq/browse/AMQ-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-869:
---------------------------
Fix Version/s: 5.3.0
(was: 5.2.0)
> 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
> Fix For: 5.3.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
