You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2012/07/19 22:05:35 UTC
[jira] [Created] (QPID-4158) HA transition to CATCHUP status too
early.
Alan Conway created QPID-4158:
---------------------------------
Summary: HA transition to CATCHUP status too early.
Key: QPID-4158
URL: https://issues.apache.org/jira/browse/QPID-4158
Project: Qpid
Issue Type: Bug
Components: C++ Clustering
Affects Versions: 0.17
Reporter: Alan Conway
Assignee: Alan Conway
Fix For: 0.18
Previously we set status to CATCHUP when the BrokerReplicators bridge was initialized. This is too early, it's possible for an aborted attempt to connect to another backup to get as far as bridge init. This patch waits till we receive the first actual message from the primary before updating status to CATCHUP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Commented] (QPID-4158) HA transition to CATCHUP status too
early.
Posted by "Gordon Sim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419021#comment-13419021 ]
Gordon Sim commented on QPID-4158:
----------------------------------
I'm in favour of merging this to the 0.18 branch. It is a simple fix with very limited scope and impact (all with the HA feature) and it fixes a sporadic test failure.
> HA transition to CATCHUP status too early.
> ------------------------------------------
>
> Key: QPID-4158
> URL: https://issues.apache.org/jira/browse/QPID-4158
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
> Affects Versions: 0.17
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.18
>
>
> Previously we set status to CATCHUP when the BrokerReplicators bridge was initialized. This is too early, it's possible for an aborted attempt to connect to another backup to get as far as bridge init. This patch waits till we receive the first actual message from the primary before updating status to CATCHUP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Commented] (QPID-4158) HA transition to CATCHUP status too
early.
Posted by "Gordon Sim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419272#comment-13419272 ]
Gordon Sim commented on QPID-4158:
----------------------------------
Merged to 0.18 release branch as r1363852.
> HA transition to CATCHUP status too early.
> ------------------------------------------
>
> Key: QPID-4158
> URL: https://issues.apache.org/jira/browse/QPID-4158
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
> Affects Versions: 0.17
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.18
>
>
> Previously we set status to CATCHUP when the BrokerReplicators bridge was initialized. This is too early, it's possible for an aborted attempt to connect to another backup to get as far as bridge init. This patch waits till we receive the first actual message from the primary before updating status to CATCHUP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Commented] (QPID-4158) HA transition to CATCHUP status too
early.
Posted by "Justin Ross (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419151#comment-13419151 ]
Justin Ross commented on QPID-4158:
-----------------------------------
Reviewed by Gordon. Approved for 0.18.
> HA transition to CATCHUP status too early.
> ------------------------------------------
>
> Key: QPID-4158
> URL: https://issues.apache.org/jira/browse/QPID-4158
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
> Affects Versions: 0.17
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.18
>
>
> Previously we set status to CATCHUP when the BrokerReplicators bridge was initialized. This is too early, it's possible for an aborted attempt to connect to another backup to get as far as bridge init. This patch waits till we receive the first actual message from the primary before updating status to CATCHUP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Commented] (QPID-4158) HA transition to CATCHUP status too
early.
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418639#comment-13418639 ]
Alan Conway commented on QPID-4158:
-----------------------------------
Fixed on trunk r1363520
Request merge to 0.18
> HA transition to CATCHUP status too early.
> ------------------------------------------
>
> Key: QPID-4158
> URL: https://issues.apache.org/jira/browse/QPID-4158
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
> Affects Versions: 0.17
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.18
>
>
> Previously we set status to CATCHUP when the BrokerReplicators bridge was initialized. This is too early, it's possible for an aborted attempt to connect to another backup to get as far as bridge init. This patch waits till we receive the first actual message from the primary before updating status to CATCHUP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Resolved] (QPID-4158) HA transition to CATCHUP status too
early.
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway resolved QPID-4158.
-------------------------------
Resolution: Fixed
> HA transition to CATCHUP status too early.
> ------------------------------------------
>
> Key: QPID-4158
> URL: https://issues.apache.org/jira/browse/QPID-4158
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
> Affects Versions: 0.17
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.18
>
>
> Previously we set status to CATCHUP when the BrokerReplicators bridge was initialized. This is too early, it's possible for an aborted attempt to connect to another backup to get as far as bridge init. This patch waits till we receive the first actual message from the primary before updating status to CATCHUP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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