[rabbitmq-discuss] HA + Clustering in EC2 with Amazon Autoescale

Marek Majkowski majek04 at gmail.com
Wed Sep 8 14:13:08 BST 2010

Well, in that case just hardcode some magical cookie, put it in
user-data EC2 script or something like that. Create a function
to read the host names of the hosts in a cluster and use that
to automate the setup.

Sounds like few dozen lines of shell, but should be possible.
I don't think anyone has done it yet..


On Wed, Sep 8, 2010 at 11:00, Jaime Martinez <jaimemm at gmail.com> wrote:
> We are just making a POC of how to use new Amazon's autoescale feature, so
> we can add instances based on rules. Those instances must contain rabbitmq
> servers in a cluster, all in the same cluster.
> From what I read, and what you're confirming, it looks like there's no
> starightforward way of making it automatically.
> Any ideas?
> With regards
> On Wed, Sep 8, 2010 at 11:45 AM, Marek Majkowski <majek04 at gmail.com> wrote:
>> Jaime,
>> On Fri, Sep 3, 2010 at 11:22, Jaime Martinez <jaimemm at gmail.com> wrote:
>> > Here is the scenario:
>> > - More than 1 pair of Active + Passive RabbitMQ servers per EC2
>> > instance,
>> > all of them in cluster.
>> > - Autoescale will start a new EC2 instances and has to add the new
>> > RabbitMQ
>> > HA servers to the same cluster as the previous instances
>> > It looks pretty tricky since to add server instances to a cluster is
>> > necessary to know their identifiers. Did anyone tried this? What would
>> > it be
>> > the right way of doing it?
>> Yes, in order to join RabbitMQ nodes into a cluster you need to know the
>> shared
>> cookie and the addresses of all hosts in the cluster, as described here:
>>   http://www.rabbitmq.com/clustering.html
>> In my opinion clustering is not perfect. It helps scaling only for a set
>> of use
>> cases. Basically, to exploit the benefits you need to really know what
>> you're
>> doing. Generally, I wouldn't recommend it. Also, correctly configuring
>> clustering with HA is really tricky.
>> Saying that, I'd recommend just upgrading EC2 host if you need more
>> capacity.
>> Store the persistent data on EBS and when you need more power - just
>> reattach EBS to a host with more CPU power. Sure, that's not
>> zero-downtime,
>> but at least it's simple and manageable.
>> Cheers,
>>  Marek Majkowski
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list