[jira] [Commented] (QPID-4126) HA primary times out expected backups.

2012-07-11 Thread Justin Ross (JIRA)

[ 
https://issues.apache.org/jira/browse/QPID-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411926#comment-13411926
 ] 

Justin Ross commented on QPID-4126:
---

Reviewed by Gordon.  Approved for 0.18.

> HA primary times out expected backups.
> --
>
> Key: QPID-4126
> URL: https://issues.apache.org/jira/browse/QPID-4126
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Clustering
>Affects Versions: 0.17
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.18
>
>
> After a failure, the newly-promoted primary broker guards messages for each 
> of the backups that were connected at the time of the failure. It waits for 
> them to reconnect to the new primary before becoming active.
> This patch introduces a time-out so that if an expected backup fails to 
> fail-over within the time limit, the primary will cancel the guards for that 
> backup and carry on.

--
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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Commented] (QPID-4126) HA primary times out expected backups.

2012-07-11 Thread Alan Conway (JIRA)

[ 
https://issues.apache.org/jira/browse/QPID-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411858#comment-13411858
 ] 

Alan Conway commented on QPID-4126:
---

Fixed on trunk r1359872

> HA primary times out expected backups.
> --
>
> Key: QPID-4126
> URL: https://issues.apache.org/jira/browse/QPID-4126
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Clustering
>Affects Versions: 0.17
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.18
>
>
> After a failure, the newly-promoted primary broker guards messages for each 
> of the backups that were connected at the time of the failure. It waits for 
> them to reconnect to the new primary before becoming active.
> This patch introduces a time-out so that if an expected backup fails to 
> fail-over within the time limit, the primary will cancel the guards for that 
> backup and carry on.

--
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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Commented] (QPID-4126) HA primary times out expected backups.

2012-07-11 Thread Alan Conway (JIRA)

[ 
https://issues.apache.org/jira/browse/QPID-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411856#comment-13411856
 ] 

Alan Conway commented on QPID-4126:
---

Reviewed by gsim  https://reviews.apache.org/r/5890/#review9062

Fixed on 0.18:

r1360348 | aconway | 2012-07-11 14:55:17 -0400 (Wed, 11 Jul 2012) | 10 lines

QPID-4126: HA primary times out expected backups.

After a failure, the newly-promoted primary broker guards messages for each of
the backups that were connected at the time of the failure. It waits for them to
reconnect to the new primary before becoming active.

This patch introduces a time-out so that if an expected backup fails to
fail-over within the time limit, the primary will cancel the guards for that
backup and carry on.


> HA primary times out expected backups.
> --
>
> Key: QPID-4126
> URL: https://issues.apache.org/jira/browse/QPID-4126
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Clustering
>Affects Versions: 0.17
>Reporter: Alan Conway
>Assignee: Alan Conway
>
> After a failure, the newly-promoted primary broker guards messages for each 
> of the backups that were connected at the time of the failure. It waits for 
> them to reconnect to the new primary before becoming active.
> This patch introduces a time-out so that if an expected backup fails to 
> fail-over within the time limit, the primary will cancel the guards for that 
> backup and carry on.

--
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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org