You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "michael j. goulish (JIRA)" <qp...@incubator.apache.org> on 2008/10/27 14:38:44 UTC
[jira] Created: (QPID-1404) Client-side failover
Client-side failover
--------------------
Key: QPID-1404
URL: https://issues.apache.org/jira/browse/QPID-1404
Project: Qpid
Issue Type: Improvement
Reporter: michael j. goulish
This code successfully failed over (upon one killed broker in a 3-cluster) 200 times, with both sender and listener failing over, and with the sending client running at full speed (no pauses between messages.)
Problems with it still outstanding:
1. lots of repetitive code in FailoverSession.cpp -- aconway is planning to replace all this code with generated code.
2. It doesn't use the tagged-arguments interface -- but I believe that will also be fixed by switching to generated code.
3. No message-replay as yet, to insure at-least-once delivery.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1404) Client-side failover
Posted by "Rafael H. Schloming (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafael H. Schloming updated QPID-1404:
--------------------------------------
Affects Version/s: M4
> Client-side failover
> --------------------
>
> Key: QPID-1404
> URL: https://issues.apache.org/jira/browse/QPID-1404
> Project: Qpid
> Issue Type: Improvement
> Affects Versions: M4
> Reporter: michael j. goulish
> Attachments: failover_rc5.diff
>
>
> This code successfully failed over (upon one killed broker in a 3-cluster) 200 times, with both sender and listener failing over, and with the sending client running at full speed (no pauses between messages.)
> This was tested on RHEL 5.2
> Problems with it still outstanding:
> 1. lots of repetitive code in FailoverSession.cpp -- aconway is planning to replace all this code with generated code.
> 2. It doesn't use the tagged-arguments interface -- but I believe that will also be fixed by switching to generated code.
> 3. No message-replay as yet, to insure at-least-once delivery.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1404) Client-side failover
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-1404:
-----------------------------------
Component/s: C++ Broker
Adding component C++ broker
> Client-side failover
> --------------------
>
> Key: QPID-1404
> URL: https://issues.apache.org/jira/browse/QPID-1404
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Affects Versions: M4
> Reporter: michael j. goulish
> Attachments: failover_rc5.diff
>
>
> This code successfully failed over (upon one killed broker in a 3-cluster) 200 times, with both sender and listener failing over, and with the sending client running at full speed (no pauses between messages.)
> This was tested on RHEL 5.2
> Problems with it still outstanding:
> 1. lots of repetitive code in FailoverSession.cpp -- aconway is planning to replace all this code with generated code.
> 2. It doesn't use the tagged-arguments interface -- but I believe that will also be fixed by switching to generated code.
> 3. No message-replay as yet, to insure at-least-once delivery.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1404) Client-side failover
Posted by "michael j. goulish (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
michael j. goulish updated QPID-1404:
-------------------------------------
Description:
This code successfully failed over (upon one killed broker in a 3-cluster) 200 times, with both sender and listener failing over, and with the sending client running at full speed (no pauses between messages.)
This was tested on RHEL 5.2
Problems with it still outstanding:
1. lots of repetitive code in FailoverSession.cpp -- aconway is planning to replace all this code with generated code.
2. It doesn't use the tagged-arguments interface -- but I believe that will also be fixed by switching to generated code.
3. No message-replay as yet, to insure at-least-once delivery.
was:
This code successfully failed over (upon one killed broker in a 3-cluster) 200 times, with both sender and listener failing over, and with the sending client running at full speed (no pauses between messages.)
Problems with it still outstanding:
1. lots of repetitive code in FailoverSession.cpp -- aconway is planning to replace all this code with generated code.
2. It doesn't use the tagged-arguments interface -- but I believe that will also be fixed by switching to generated code.
3. No message-replay as yet, to insure at-least-once delivery.
> Client-side failover
> --------------------
>
> Key: QPID-1404
> URL: https://issues.apache.org/jira/browse/QPID-1404
> Project: Qpid
> Issue Type: Improvement
> Reporter: michael j. goulish
>
> This code successfully failed over (upon one killed broker in a 3-cluster) 200 times, with both sender and listener failing over, and with the sending client running at full speed (no pauses between messages.)
> This was tested on RHEL 5.2
> Problems with it still outstanding:
> 1. lots of repetitive code in FailoverSession.cpp -- aconway is planning to replace all this code with generated code.
> 2. It doesn't use the tagged-arguments interface -- but I believe that will also be fixed by switching to generated code.
> 3. No message-replay as yet, to insure at-least-once delivery.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1404) Client-side failover
Posted by "michael j. goulish (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
michael j. goulish updated QPID-1404:
-------------------------------------
Attachment: failover_rc5.diff
> Client-side failover
> --------------------
>
> Key: QPID-1404
> URL: https://issues.apache.org/jira/browse/QPID-1404
> Project: Qpid
> Issue Type: Improvement
> Reporter: michael j. goulish
> Attachments: failover_rc5.diff
>
>
> This code successfully failed over (upon one killed broker in a 3-cluster) 200 times, with both sender and listener failing over, and with the sending client running at full speed (no pauses between messages.)
> This was tested on RHEL 5.2
> Problems with it still outstanding:
> 1. lots of repetitive code in FailoverSession.cpp -- aconway is planning to replace all this code with generated code.
> 2. It doesn't use the tagged-arguments interface -- but I believe that will also be fixed by switching to generated code.
> 3. No message-replay as yet, to insure at-least-once delivery.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.