From a04ae99fb30d44e9ebc3f3a59b849f125f751084 Mon Sep 17 00:00:00 2001 From: Yuce Tekol Date: Fri, 13 Apr 2018 03:41:59 +0300 Subject: [PATCH] updated cluster tutorial with feedback --- docs/tutorials.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorials.md b/docs/tutorials.md index 4d1a06c42..5e0d5376d 100644 --- a/docs/tutorials.md +++ b/docs/tutorials.md @@ -70,7 +70,7 @@ We now should have `pilosa.local.gossip32` in the current directory with 32 rand Pilosa supports passing configuration items using the command line, environment variables or a configuration file. We will use the last option in this tutorial and create three configuration files for our three nodes. -One of the nodes in the cluster must be chosen as the *coordinator*. We choose the first node as the coordinator in this tutorial. +One of the nodes in the cluster must be chosen as the *coordinator*. We choose the first node as the coordinator in this tutorial. The coordinator is only important during cluster resizing operations, and otherwise acts like any other node in the cluster. In the future, the coordinator will be chosen transparently by distributed consensus, and this option will be deprecated. Create `node1.config.toml` in the project directory and paste the following in it: