two nodes + shared storage

[jo...@acuityscheduling.com]

Hello,

I currently have a single rabbitmq node using local storage. I'd like to move to two nodes, shared storage (SAN mount), along with a floating IP (keepalived).

I understand that both nodes need to have the same node name along with the same erlang cookie. My question is the following:

In this sort of configuration, should both nodes be running rabbitmq at all times OR do I need to make sure only a single node is running rabbitmq against the shared SAN mount.

In other words, if I have two rabbitmq instances running at the same time while using the same shared storage, could that be trouble?

Thanks!

-jp

[Michael Klishin]

Hi Josh,

You should be able to find a few discussions on this topic in list archives. In general,

some users still use Pacemaker or similar tools [1] successfully.

I personally am very wary recommending a shared database. Nodes do not assume concurrent access.

There is a way to do a standby node with exchange federation and a message TTL policy. This also

has been discussed on this list in the past and the recommendations haven't really changed in the last few years.

A few relevant threads (first hits):

https://groups.google.com/d/msg/rabbitmq-users/sauOyqY4Pf0/dFYS6fWHBwAJ

https://groups.google.com/d/msg/rabbitmq-users/4bu1qTCnniU/T3HTdQLzAQAJ

This approach sounds relevant (even though the focus on solving a different problem):

https://content.pivotal.io/blog/blue-green-application-deployments-with-rabbitmq

https://www.youtube.com/watch?v=S2oO-t-E38c

1. http://www.rabbitmq.com/pacemaker.html

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Josh Pollara]

Thank you for the response! After reading this and discussing on Slack, seems like the best course of action is to just set up a rabbitmq cluster.

To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

--
You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rabbitmq-users/SH4vScWN0c8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rabbitmq-users+unsubscribe@googlegroups.com.