[jira] [Updated] (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: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
[jira] [Updated] (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:all-tabpanel ] Justin Ross updated QPID-2357: -- Assignee: Alan Conway > 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (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:all-tabpanel ] Justin Ross updated QPID-2357: -- Assignee: (was: Alan Conway) > 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 > 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
[jira] Updated: (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:all-tabpanel ] john dunning updated QPID-2357: --- Attachment: qpid-sync-proposed-2.diff Revised patch, after comments from aconway. > 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 > 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. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (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:all-tabpanel ] john dunning updated QPID-2357: --- Attachment: qpid-sync-proposed.diff Attached patch fixes this problem, for at least simple cases. NB that there are other ways to get OIDs out of sync during an update operation, most notably by having timers fire at an inopportune time. That bug is being worked separately. Comments welcome. > 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 > Attachments: 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. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
