[bitnami/rabbitmq] Use of clustering.rebalance is not documented properly

[utkarshmani1997]

Name and Version

bitnami/rabbitmq 15.2.3

What is the problem this feature will solve?

There are a few instances of cluster.rebalance in the chart but it's not clear how and where is this flag really used.
I found an instance where we are only setting the env RABBITMQ_CLUSTER_REBALANCE to true, but where exactly is this env variable used?
I want to understand its effect on Quorum Queues and whether it is required or not.

What is the feature you are proposing to solve the problem?

Having a clear comment on this flag about its uses will help in understanding its use cases and whether it is required or not in Quorum Queues.

[carrodher]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

[utkarshmani1997]

Thanks @carrodher i am happy to contribute. But, i would like to understand how its getting used. We can discuss the approach regarding the same.

[utkarshmani1997]

@javsalgar @carrodher any updates on the above query?

[javsalgar]

Hi,

The env var is used here: https://github.com/bitnami/containers/blob/d42d276a324c917bc0d575d6f6e7cdccec24c50e/bitnami/rabbitmq/4.0/debian-12/rootfs/opt/bitnami/scripts/rabbitmq/run.sh#L21

That script is run after the RabbitMQ initialization.

[utkarshmani1997]

Thanks for the quick turnaround. I will update the comments about its uses.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.