cluster: add local_node settings #923
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request (PR) description
When overriding local node name (using NODENAME environment variable), clustering does not work as tinit_node is tested again hostname or fqdn. By adding the optional local_node to specify which node is the current node we can fix this issue.
Use case: a server with a public and a private interface, rabbitmq cluster nodes communicates through the private interface while hostname and fqdn resolves to the public interface (and that can't be changed because of other dependencies on the server). The only solution is to use dedictated name for the private interface.