I have been using this. There is a version of connect that can take a set of qpid servers (urls). You actually end up connecting to one of them.
You need to install openais to do clustering (libraries and configure it and start aisexec on each server). When qpid is built with cpg (part of openais) qpid can take a group either in the command line or via the config file. The qpid servers broadcast state to one another via cpg/openais which uses multicast. The set of commands you issue to either server are broadcast to the other. If one goes down and then comes back up the server state is quickly resync'd. The performance is slightly less than running in a non-clustered mode, but is still quite good in my opinion. You can use a FailoverManager from the client to handle the Transport exceptions you'll get when the server you are connected to goes down. Adam On Wed, Feb 11, 2009 at 6:51 AM, chenta <[email protected]> wrote: > > I construct a broker cluster and I want to use c++ client to connect it. > > I have three questions: > 1. How do clients join the cluster? If the client connect to one of the > broker in the cluster, does it also means that it connect to the cluster? > Can I use cluster name to join to cluster? > 2. How do I specified a broker list to c++ client? > 3. Do we need a broker list to make failover exchange works? > > Thanks, > Chenta > -- > View this message in context: > http://n2.nabble.com/About-broker-list-tp2308196p2308196.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:[email protected] > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
