You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2013/07/29 17:53:49 UTC
[jira] [Commented] (QPID-2357) Broker boot sequence doesn't
synchronize when clustered.
[ https://issues.apache.org/jira/browse/QPID-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722559#comment-13722559 ]
Justin Ross commented on QPID-2357:
-----------------------------------
Change appears to be 904270, not 904268. http://svn.apache.org/viewvc?view=revision&revision=904270
> 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
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org