qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Terance Dias <tera...@socialtwist.com>
Subject Re: qpid async replication and failover
Date Fri, 05 Oct 2012 09:40:38 GMT
Thanks a lot for your reply Gordon.

We are using the replication described at  http://qpid.apache.org/books/**
We are running on Ubuntu.

We decided to go with this kind of replication because it allowed HA
solution across networks. Does the new mechanism work across networks or
are the nodes required to be in the same network?
Also, I'm new to Linux. So I just wanted to know how rgmanager works. Does
it run on a separate node and monitors the cluster nodes? In that case can
it be a single point of failure?
Also, Please let me know if you know if anybody has deployed the new
cluster mechanism in production.


On Fri, Oct 5, 2012 at 12:34 PM, Gordon Sim <gsim@redhat.com> wrote:

> On 10/04/2012 01:29 PM, Terance Dias wrote:
>> We are trying out qpid with async replication. We have multiple clients
>> accessing the master node for reading and writing messages. If the master
>> node goes down, the client that tried to access it failsover to the slave
>> node.
>> The problem that we are facing is that if the master recovers and one of
>> the other clients that had not tried to access the master node (while it
>> as
>> down) would not have failed over to the slave and will continue to access
>> the master. So I could end up having some of my clients accessing the
>> master while some are accessing the slave. This could lead to inconsistent
>> state of the queues.
>> My question is how do i get all my clients to failover all at once. I
>> realize that perhaps this is not a problem that qpid should solve and
>> maybe
>> should be solved outside of qpid but I just want to know if anybody has
>> faced similar problem before. I guess setting up circular replication (so
>> that both nodes are in sync) could help but qpid doesn't support circular
>> replication. Any thoughts?
> Is the async replication you are using as described here:
> http://qpid.apache.org/books/**trunk/AMQP-Messaging-Broker-**
> CPP-Book/html/queue-state-**replication.html<http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/queue-state-replication.html>
> ?
> If so you may be interested in a newer and more powerful mechanism:
> http://qpid.apache.org/books/**trunk/AMQP-Messaging-Broker-**
> CPP-Book/html/ch01s14.html<http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s14.html>
> and
> http://qpid.apache.org/books/**trunk/AMQP-Messaging-Broker-**
> CPP-Book/html/chap-Messaging_**User_Guide-Active_Passive_**Cluster.html<http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Active_Passive_Cluster.html>
> This new HA module is available in the 0.18 release and will replace both
> the active-active cluster and the async queue replication from release 0.20.
> It includes the ability to reject clients when not the master, replication
> can be stopped and started simply (a problem with the old approach) and
> acknowledgement to publishers is delayed until replicated (which is useful
> for client based replay).
> The actual management of brokers (promotion of master etc) is done using
> rgmanager or similar cluster management tool. At present there are scripts
> only for rgmanager, but it would not be difficult I don't think to use
> pacemaker or some other tool.
> What platform are you running on?
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.**org<users-unsubscribe@qpid.apache.org>
> For additional commands, e-mail: users-help@qpid.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message