Update RELEASE_DISTRIBUTION docs #13658
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Nodes using short names can still be connected across machines.
See question 1. in this thread. I also verified this with two machines on a local network by adding an entry to
/etc/hosts, such that the short name is resolved to the peer IP.My understanding is that the resolution is exactly the same. Picking one or the other only determines if the validation requires FQDN or rejects FQDN, and nodes can only connect to other nodes using the same mode. I am interested to know what was the original motivation for two distinct modes in the first place (in Erlang), if someone is aware, please leave a comment.