From 350ce95e632349df90bb3e515230ad6c6b1ae404 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=BC=A0=E7=82=8E=E6=B3=BC?= Date: Sun, 3 Mar 2024 14:09:52 +0800 Subject: [PATCH] Doc: fix typo: n0 should be n1 in faq.md --- openraft/src/docs/faq/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openraft/src/docs/faq/faq.md b/openraft/src/docs/faq/faq.md index 4bfef85c3..ffc58c195 100644 --- a/openraft/src/docs/faq/faq.md +++ b/openraft/src/docs/faq/faq.md @@ -35,7 +35,7 @@ Excessive error logging, like `ERROR openraft::replication: 248: RPCError err=Ne There are two ways to initialize a raft cluster, assuming there are three nodes, `n1, n2, n3`: 1. Single-step method: Call `Raft::initialize()` on any one of the nodes with the configuration of all 3 nodes, e.g. `n2.initialize(btreeset! {1,2,3})`. -2. Incremental method: First, call `Raft::initialize()` on `n1` with configuraion containing `n1` itself, e.g., `n0.initialize(btreeset! {1})`. Subsequently use `Raft::change_membership()` on `n1` to add `n2` and `n3` into the cluster. +2. Incremental method: First, call `Raft::initialize()` on `n1` with configuraion containing `n1` itself, e.g., `n1.initialize(btreeset! {1})`. Subsequently use `Raft::change_membership()` on `n1` to add `n2` and `n3` into the cluster. Employing the second method provides the flexibility to start with a single-node cluster for testing purposes and subsequently expand it to a three-node cluster for deployment in a production environment.