[rabbitmq-discuss] Using rabbitmq (v3) clusters in AWS..

[yossie]

Currently I have an application that uses rabbitmq.

There are one or more web servers in a given amazon zone that are configured
to talk to a matching rabbitmq cluster in their own zone through a ELB (one
per zone.)  The web servers in all zones are all accessed through a single
multizone ELB.  This works.  We are using "auto-discovery" which is good
when instances don't move or are added/deleted.  We would like to switch to
an autoscaled model.  This means we can't automatically link up rabbitmq
clusters via config files and, instead, have to do so using the command line
tools.  My plan is:

1) new instance starting up will use an IAM account with limited access to
find it's own zone (can do from metadata), then figure out the name of it's
elb, then figure out other instances on the same elb, and from those get the
ip address, and do a join_cluster to one of them.

2) a cron job will wake up periodically and using a similar technique, get a
list of any instances that are no longer around but are referenced in the
cluster and issue forget_cluster_node on their behalf.

I note that disk vs ram rabbitmq (we are disk right now) difficultywill
present difficulty but I think the general idea outlined above will do the
job.

I am relatively new (OK, brand new) to rabbitmq so it is likely that I am
not entirely clear on the concepts.  I am seeking advice on how best to
handle this use case.

Thank you in advance for all help - Yossie



--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Using-rabbitmq-v3-clusters-in-AWS-tp33344.html
Sent from the RabbitMQ mailing list archive at Nabble.com.