-
Notifications
You must be signed in to change notification settings - Fork 733
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New guide: Cluster Formation #298
Conversation
Which documents automatic cluster formation procedure and the pluggable peer discovery mechanisms introduced in 3.7.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few typos.
</p> | ||
|
||
<p> | ||
Nodes that previously were cluster members will try to contact |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence needs rewording.
<doc:heading>DNS Peer Discovery Backend</doc:heading> | ||
|
||
<p> | ||
Another build-in peer discovery mechanism as of RabbitMQ 3.7.0 is DNS-based. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
build-in => built-in
The following example in the classic config format. The 2nd | ||
member of the <code>rabbit.cluster_nodes</code> tuple is the | ||
node type to use for the current node. In the vast majority of | ||
cases all nodes should be <code>disc</code>nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing space between disc
and nodes
</pre> | ||
</p> | ||
<p> | ||
The following example in the classic config format. The 2nd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing the verb on this sentence. Maybe uses the classic config format
?
<code>autocluster.peer_discovery_backend</code> is the key | ||
that controls what discovery module (implementation) is used. | ||
The module has to implement the <a | ||
href="https://github.com/rabbitmq/rabbitmq-server/blob/master/src/rabbit_peer_discovery.erl">rabbit_peer_discovery</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be rabbit_peer_discovery_backend
at https://github.com/rabbitmq/rabbitmq-common/blob/master/src/rabbit_peer_discovery_backend.erl
Should be corrected now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo.
</p> | ||
|
||
<p> | ||
If a node node previously was a cluster member, it will try to contact |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"node node" => "node"
Which documents automatic cluster formation procedure and
the pluggable peer discovery mechanisms introduced in 3.7.0.
Part of rabbitmq/rabbitmq-server#988 as well as rabbitmq/rabbitmq-server#486.