[Questions] How to Better Utilize RabbitMQ in Containerized Deployment Scenarios

[dormanze]

Community Support Policy

• I have read RabbitMQ's Community Support Policy
• I run RabbitMQ 4.x, the only series currently covered by community support
• I promise to provide all relevant information (versions, logs from all nodes, rabbitmq-diagnostics output, detailed reproduction steps)

RabbitMQ version used

4.1.1

Erlang version used

27.3.x

Operating system (distribution) used

linux

How is RabbitMQ deployed?

Generic binary package

rabbitmq-diagnostics status output

See https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics

# PASTE OUTPUT HERE, BETWEEN BACKTICKS

Logs from node 1 (with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 2 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 3 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

rabbitmq.conf

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location

# PASTE rabbitmq.conf HERE, BETWEEN BACKTICKS

Steps to deploy RabbitMQ cluster

set /etc/hosts and config rabbitmq

Steps to reproduce the behavior in question

start rabbitmq container and destroy one

advanced.config

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location

# PASTE advanced.config HERE, BETWEEN BACKTICKS

Application code

# PASTE CODE HERE, BETWEEN BACKTICKS

Kubernetes deployment file

# Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
# PASTE YAML HERE, BETWEEN BACKTICKS

What problem are you trying to solve?

I have deployed my RabbitMQ using containerization. During startup, I modify the /etc/hosts file using sudo to add information about other RabbitMQ nodes. After the RabbitMQ cluster is fully formed, some of my RabbitMQ containers may be destroyed and rebuilt during runtime, causing the IP addresses of the rebuilt RabbitMQ containers to change. This necessitates frequent use of scheduled scripts to update /etc/hosts. Is there a better solution, such as adapting to DNS, where each of my containers has a fixed domain name, for example: rabbitmq-0-headless.kube-system.svc.cluster.local.

[mkuratczyk]

It's not clear if you're using Kubernetes or not, but your Kubernetes-inspired example is exactly right. RabbitMQ assumes hostnames are stable (hostname is part of the node's identity) and you should make it so that IP changes are handled transparently. Kubernetes does it by automatically updating DNS records and it's a great way to accomplish stable hostnames despite IP changes.

[dormanze]

I found some solution in the document and will attempt to investigate it.Thank you for your response.
https://www.rabbitmq.com/docs/clustering#cluster-formation-requirements
https://www.erlang.org/doc/apps/erts/inet_cfg.html

[michaelklishin]

Besides the Networking guide, there really isn't much to add to those two.