You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by David Zhou <da...@gmail.com> on 2010/04/09 11:19:07 UTC

failover problem in a cluster (C++ broker, python client)

Hi all,

i have set up a cluster of C++ broker A and B, and brokers in the cluster
are synced by corosync.
i can send a message to broker A and retrieve it from broker B.

my question is:

 Is there any automated way of failover for python client?
 (for java or c++ client, there seems to have a FailoverManager to handle
this problem and we just supply 
  the FailoverManager an url that specifies some candidate brokers.)
 But for python client, in the example illustrated in the doc, i haven't see
a similar case of failover handling 
 with FailoverManager.
 If there is none, does anyone have a hint for me to implement failover with
python client? 
 
Any suggestions are appreciated!
Thanks a million.

Best,
David.
-- 
View this message in context: http://n2.nabble.com/failover-problem-in-a-cluster-C-broker-python-client-tp4876111p4876111.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: failover problem in a cluster (C++ broker, python client)

Posted by Carton <da...@gmail.com>.
Hi Gordon,

Thank for your help!

It's version 0.5 i used. http://qpid.apache.org/docs/api/python/html/index.html
I am glad to see the messaging module in the version 0.6.
It looks good! :)


2010/4/10 Gordon Sim <gs...@redhat.com>:
> On 04/09/2010 10:19 AM, David Zhou wrote:
>>
>> Hi all,
>>
>> i have set up a cluster of C++ broker A and B, and brokers in the cluster
>> are synced by corosync.
>> i can send a message to broker A and retrieve it from broker B.
>>
>> my question is:
>>
>>  Is there any automated way of failover for python client?
>>  (for java or c++ client, there seems to have a FailoverManager to handle
>> this problem and we just supply
>>   the FailoverManager an url that specifies some candidate brokers.)
>>  But for python client, in the example illustrated in the doc, i haven't
>> see
>> a similar case of failover handling
>>  with FailoverManager.
>>  If there is none, does anyone have a hint for me to implement failover
>> with
>> python client?
>
> There is a newer api that supports automatic reconnect and replay; that is
> in the messaging module. There have been a few changes around some method
> names for that api recently but it is settling down now. What version are
> you using, or are you working from trunk?
>
> (Btw there is an equivalent api in c++ now that aims to make the experience
> using these two clients more uniform. The failover support in that is nicer
> in my view than the 0-10 specific api.)
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>



-- 
Sincerely,
David

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: failover problem in a cluster (C++ broker, python client)

Posted by Gordon Sim <gs...@redhat.com>.
On 04/09/2010 10:19 AM, David Zhou wrote:
>
> Hi all,
>
> i have set up a cluster of C++ broker A and B, and brokers in the cluster
> are synced by corosync.
> i can send a message to broker A and retrieve it from broker B.
>
> my question is:
>
>   Is there any automated way of failover for python client?
>   (for java or c++ client, there seems to have a FailoverManager to handle
> this problem and we just supply
>    the FailoverManager an url that specifies some candidate brokers.)
>   But for python client, in the example illustrated in the doc, i haven't see
> a similar case of failover handling
>   with FailoverManager.
>   If there is none, does anyone have a hint for me to implement failover with
> python client?

There is a newer api that supports automatic reconnect and replay; that 
is in the messaging module. There have been a few changes around some 
method names for that api recently but it is settling down now. What 
version are you using, or are you working from trunk?

(Btw there is an equivalent api in c++ now that aims to make the 
experience using these two clients more uniform. The failover support in 
that is nicer in my view than the 0-10 specific api.)


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org