[rabbitmq-discuss] High availability questions
mcintoshj at gmail.com
Thu Dec 6 03:19:43 GMT 2012
Design we use:
Shovel to a virtual ip rabbit cluster.
Rabbit consumers on that cluster.
Start new cluster.
Can point consumers to hard coded cluster.
Shift shovel and/or change VIP to point to new cluster.
When all messages on old consumers cleaned, shut them down point em to new cluster.
Our consumers are java apps built into rpms we deploy, so updates are just a restart/new rpm deploy
This is pretty rough but hope it helps!
Sent from my iPhone
On Dec 5, 2012, at 9:00 PM, Chris Toomey <ctoomey at gmail.com> wrote:
> Belated follow-up on this thread. Can you talk more about how you manage
> this? E.g., how do you ensure that clients continue consuming from the old
> cluster until all the messages published to it have been consumed? And
> during the transition time, consuming clients consume from both old and new
> cluster, right? What hardware/software do you use to gradually shift
> publishing from old to new cluster?
> We're just now designing and implementing our infrastructure and apps so
> would like to get it as right as possible from the beginning. Anyone else
> using/recommend other approaches to this problem?
> Laing, Michael P. wrote
>> We bring up parallel infrastructure with a complete new cluster and
>> gradually shift load to it using weighted routing.
>> This won't work for everybody, but we have designed our apps with this in
>> From: Chris Toomey <
>> That's unfortunate about having to shut down the whole cluster to upgrade
>> it -- it means that our applications will need to have some additional HA
>> queueing mechanism upstream to buffer up the messages to be published
>> during the downtime :-(.
>> What kinds of solutions are people using for that problem?
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/High-availability-questions-tp23690p23889.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss