fix node3 config; ensure hosts can be accessed; /status output

This commit is contained in:
Yuce Tekol 2017-10-21 01:41:28 +03:00
parent 9686edbca5
commit e74aa43dd0
No known key found for this signature in database
GPG key ID: CB59E46D2FB90573

View file

@ -107,7 +107,7 @@ Create `node3.config.toml` in the project directory and paste the following in i
# node3.config.toml
data-dir = "node3_data"
bind = "https://01.pilosa.local:10503"
bind = "https://03.pilosa.local:10503"
[cluster]
hosts = ["https://01.pilosa.local:10501", "https://02.pilosa.local:10502", "https://03.pilosa.local:10503"]
@ -137,6 +137,15 @@ Before running the cluster, let's make sure `01.pilosa.local`, `02.pilosa.local`
sudo sh -c 'printf "\n127.0.0.1 01.pilosa.local 02.pilosa.local 03.pilosa.local\n" >> /etc/hosts'
```
Ensure we can access the hosts in the cluster:
```
ping -c 1 01.pilosa.local
ping -c 1 02.pilosa.local
ping -c 1 03.pilosa.local
```
If any of the commands above return `ping: unknown host`, check your `/etc/hosts` contains the failed hostname.
#### Running the Cluster
Let's open three terminal windows and run each node in its window. This will enable us to better observe what's happening on which node.
@ -166,7 +175,10 @@ curl -k --ipv4 https://01.pilosa.local:10501/status
The `-k` flag is used to tell curl that it shouldn't bother with checking the certificate the server provides and `--ipv4` workarounds an issue on MacOS where the curl requests take a long time if the address resolves to `127.0.0.1`. You can leave it out on Linux and WSL.
The output to the command above should show that all nodes are `UP`.
All nodes should be in the `UP` state:
```
{"status":{"Nodes":[{"Host":"01.pilosa.local:10501","State":"UP"},{"Host":"02.pilosa.local:10502","State":"UP"},{"Host":"03.pilosa.local:10503","State":"UP"}]}}
```
#### Running Queries