From a331a1143aa80fe57b1c4eb3abf2e59d83bdefd0 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Thu, 23 May 2019 13:08:17 -0500 Subject: [PATCH] Update auto-configuration.md --- nats_streaming/clustering/auto-configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nats_streaming/clustering/auto-configuration.md b/nats_streaming/clustering/auto-configuration.md index 2a19c63..bd193e2 100644 --- a/nats_streaming/clustering/auto-configuration.md +++ b/nats_streaming/clustering/auto-configuration.md @@ -1,6 +1,6 @@ # Auto Configuration -We can also bootstrap a NATS Streaming cluster by starting one server as the seed node using the `-cluster_bootstrap` flag. This node will elect itself leader, so it's important to avoid starting multiple servers as seed. Once a seed node is started, other servers will automatically join the cluster. If the server is recovering, it will use the recovered cluster configuration. +We can also bootstrap a NATS Streaming cluster by starting **one server** as the seed node using the `-cluster_bootstrap` flag. This node will elect itself leader, **so it's important to avoid starting multiple servers as seed**. Once a seed node is started, other servers will automatically join the cluster. If the server is recovering, it will use the recovered cluster configuration. Here is an example of starting three servers in a cluster by starting one as the seed and letting the others automatically join: @@ -14,4 +14,4 @@ nats-streaming-server -store file -dir store-c -clustered -nats_server nats://lo For a given cluster ID, if more than one server is started with `cluster_bootstrap` set to true, each server with this parameter will report the misconfiguration and exit. -The very first server that bootstrapped the cluster can be restarted, however, the operator must remove the datastores of the other servers that were incorrectly started with the bootstrap parameter before attempting to restart them. If they are restarted -even without the `-cluster_bootstrap` parameter- but with existing state, they will once again start as a leader. +The very first server that bootstrapped the cluster can be restarted, however, the operator **must remove the datastores** of the other servers that were incorrectly started with the bootstrap parameter before attempting to restart them. If they are restarted -even without the `-cluster_bootstrap` parameter- but with existing state, they will once again start as a leader.