[rabbitmq-discuss] Upgrade 2.7.1 RabbitMQ cluster to 2.8.1 version

Wed May 23 10:04:37 BST 2012

Hi Eslam,

I guess Brendan means:
1.set up a new cluster, maybe only one node, running new version of 
rabbitmq like 2.8.1
2.redirect some of your clients to the new cluster (you can't go too fast, 
the new cluster couldn't not handle too many clients)
3.upgrade one node in the old cluster to the new version of rabbitmq
4.add the node upgraded to the new cluster
5. redirect some of your clients to the new cluster
6.repeat step 3 to 5 until all nodes upgraded and all clients redirected to 
the new cluster

To create rabbitmq cluster, rabbitmqctl command is the only way to achieve 
as I know.

On Thursday, April 5, 2012 1:02:55 AM UTC+8, Eslam El Husseiny wrote:
>
> sorry but i didn't understand the procedure of adding new physical cluster 
> running 2.8.1
> do you mean using rabbitmqctl command to new physical machine to cluster , 
> OR ?
>
> Thanks in advance 
>
> On Monday, April 2, 2012 6:35:11 AM UTC+2, Brendan Hay wrote:
>>
>> Hi Roshan,
>>
>> I would suggest you provision a _new_ physical cluster running 2.8.1
>> side by side with your old cluster, and then incrementally move
>> producers/consumers over.
>>
>> Are you using some sort of load-balancer in front of your cluster,
>> such as HAProxy or LVS?
>> What sort of service discovery do the clients use to find Rabbit?
>> (Chef, ZooKeeper, hard-coded configs, etc.)
>>
>> Regards,
>> Brendan
>>
>> On Apr 2, 3:14 am, Codevally <codeva... at gmail.com> wrote:
>> > Hi All
>> >
>> > I need to upgrade our current production 2.7.1 RabbitMQ cluster to it's 
>> new
>> > 2.8.1 version.
>> >
>> > In our production cluster, we have 2 disc node and erlang R15B 
>> installed.
>> > According to the RabbitMQ cluster guilde:
>> >
>> > "All nodes in a cluster must be running the same versions of Erlang and
>> > RabbitMQ, although they may have different plugins installed. Therefore 
>> it
>> > is necessary to stop all nodes in the cluster, then start all nodes when
>> > performing an upgrade."
>> >
>> > In our case we cannot shutdown our existing cluster, because it is 
>> heavily
>> > used to send messages across regions.
>> >
>> > Could someone please let me know how to upgrade 2.7.1 cluster without
>> > shutdown the entire cluster.
>> >
>> > Many Thanks.
>> > /Roshan
>> >
>> > _______________________________________________
>> > rabbitmq-discuss mailing list
>> > rabbitmq-disc... at lists.rabbitmq.comhttps://
>> lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120523/c6914fcf/attachment.htm>