[
https://issues.apache.org/jira/browse/QPID-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-2357:
------------------------------
Fix Version/s: 0.6
> Broker boot sequence doesn't synchronize when clustered.
> --------------------------------------------------------
>
> Key: QPID-2357
> URL: https://issues.apache.org/jira/browse/QPID-2357
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Environment: Linux
> Reporter: john dunning
> Assignee: Alan Conway
> Fix For: 0.6
>
> Attachments: qpid-sync-proposed-2.diff, qpid-sync-proposed.diff
>
>
> I discovered this when debugging something else. If you start broker 1 with
> a data-dir, and broker 2 with no data-dir or a different one, you can (almost
> always) end up with a different boot sequence. That means if you cluster
> these two together, when the updatee gets updates, he'll use different OIDs
> that the master.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
