From 7b90473eb1a633e772648eaab166d62297cde309 Mon Sep 17 00:00:00 2001 From: "Kyle J. Davis" Date: Thu, 20 Jun 2024 14:40:47 -0600 Subject: [PATCH] resolves ambigious markdown Signed-off-by: Kyle J. Davis --- topics/cluster-spec.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/topics/cluster-spec.md b/topics/cluster-spec.md index c6b5bf55..9dbc43cb 100644 --- a/topics/cluster-spec.md +++ b/topics/cluster-spec.md @@ -347,9 +347,7 @@ A node will accept another node as part of the cluster only in two ways: * If a node presents itself with a `MEET` message (`CLUSTER MEET` command). A meet message is exactly like a `PING` message, but forces the receiver to accept the node as part of -the cluster. Nodes will send `MEET` messages to other nodes **only if** the system administrator requests this via the following command: - - CLUSTER MEET ip port +the cluster. Nodes will send `MEET` messages to other nodes **only if** the system administrator requests this via `CLUSTER MEET ip port`. * A node will also register another node as part of the cluster if a node that is already trusted will gossip about this other node. So if A knows B, and B knows C, eventually B will send gossip messages to A about C. When this happens, A will register C as part of the network, and will try to connect with C.