'rafthttp: failed to find member' Error When Creating ETCD Cluster of 2 Nodes In Docker #16138
Replies: 1 comment 4 replies
-
|
Hey @Anand11Yash there are quite a few issues in the
Try something like this, it worked for me: REGISTRY=quay.io/coreos/etcd
ETCD_VERSION=3.5.9
TOKEN=my-etcd-token
CLUSTER_STATE=new
NAME_1=etcd-node-1
NAME_2=etcd-node-2
CLUSTER=${NAME_1}=http://${NAME_1}:2380,${NAME_2}=http://${NAME_2}:2381
DATA_DIR_1=etcd1
DATA_DIR_2=etcd2
docker network create etcd
# For node 1
docker run -d \
-p 2379:2379 \
-p 2380:2380 \
--volume=${DATA_DIR_1}:/etcd-data \
--network etcd \
--hostname ${NAME_1} \
--name etcd1 ${REGISTRY}:v${ETCD_VERSION} \
/usr/local/bin/etcd \
--data-dir=/etcd-data --name etcd-node-1 \
--initial-advertise-peer-urls http://${NAME_1}:2380 --listen-peer-urls http://0.0.0.0:2380 \
--advertise-client-urls http://${NAME_1}:2379 --listen-client-urls http://0.0.0.0:2379 \
--initial-cluster ${CLUSTER} \
--initial-cluster-state ${CLUSTER_STATE} --initial-cluster-token ${TOKEN}
# For node 2
docker run -d \
-p 2378:2378 \
-p 2381:2381 \
--volume=${DATA_DIR_2}:/etcd-data \
--network etcd \
--hostname ${NAME_2} \
--name etcd2 ${REGISTRY}:v${ETCD_VERSION} \
/usr/local/bin/etcd \
--data-dir=/etcd-data --name etcd-node-2 \
--initial-advertise-peer-urls http://${NAME_2}:2381 --listen-peer-urls http://0.0.0.0:2381 \
--advertise-client-urls http://${NAME_2}:2378 --listen-client-urls http://0.0.0.0:2378 \
--initial-cluster ${CLUSTER} \
--initial-cluster-state ${CLUSTER_STATE} --initial-cluster-token ${TOKEN}After running this I was able to run +------------------+---------+-------------+-------------------------+-------------------------+------------+
| ID | STATUS | NAME | PEER ADDRS | CLIENT ADDRS | IS LEARNER |
+------------------+---------+-------------+-------------------------+-------------------------+------------+
| c30625e8a8c1af | started | etcd-node-2 | http://etcd-node-2:2381 | http://etcd-node-2:2378 | false |
| 7aa84c8b1d0c8bb4 | started | etcd-node-1 | http://etcd-node-1:2380 | http://etcd-node-1:2379 | false |
+------------------+---------+-------------+-------------------------+-------------------------+------------+
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the response @jmhbnz! When I ran your command, I got "Error response from daemon: network with name etcd already exists". No issues with this as I understand that it can be skipped. When I ran etcdctl, i can see that the containers have been created. However, can you please explain how do I get them to interact with eachother now or make a cluster for them? |
Beta Was this translation helpful? Give feedback.
-
|
Also is it compulsory to only create clusters of 1, 3, 5? I was told this is the case but looking at your output, it doesn't seem that way... |
Beta Was this translation helpful? Give feedback.
-
|
Please refer to our FAQ:
A cluster of size 2 is not recommended due to having zero redundancy but additional complexity, however it does 'work'. If you followed the instructions I posted the two containers will already be operating as a cluster. You can test this by running something like: etcdctl --endpoints 127.0.0.1:2378,127.0.0.1:2379 endpoint status -w table
+----------------+------------------+---------+-----------------+---------+----------------+-----------+------------+-----------+------------+--------------------+--------+
| ENDPOINT | ID | VERSION | STORAGE VERSION | DB SIZE | DB SIZE IN USE | IS LEADER | IS LEARNER | RAFT TERM | RAFT INDEX | RAFT APPLIED INDEX | ERRORS |
+----------------+------------------+---------+-----------------+---------+----------------+-----------+------------+-----------+------------+--------------------+--------+
| 127.0.0.1:2378 | c30625e8a8c1af | 3.5.9 | | 20 kB | 16 kB | true | false | 4 | 14 | 14 | |
| 127.0.0.1:2379 | 7aa84c8b1d0c8bb4 | 3.5.9 | | 20 kB | 16 kB | false | false | 4 | 14 | 14 | |
+----------------+------------------+---------+-----------------+---------+----------------+-----------+------------+-----------+------------+--------------------+--------+
Refer: https://etcd.io/docs/v3.5/tutorials/how-to-check-cluster-status/ |
Beta Was this translation helpful? Give feedback.
-
|
I did follow the instruction and I was able to successfully able to create the status table for the 2 nodes like you did. However, when I created a new script with an extra third node, I am unable to find it in the table using Also the container is not visible when I run The output after running this script is: The output of running Additionally, the outcome of running |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone
I am trying to create an etcd cluster with 2 nodes using Docker on my system. Please note that I am doing all this on a single system.
The script that I have created for clustering is based on the commands provided on the v3.5 document for creating multi-node cluster in Docker. My script has been provided below, please let me know if there is any issue with it:
The output after running this script is as follows:
Please let me know what I am doing wrong and if my approach to creating a 2 node etcd cluster using Docker is correct or not.
Beta Was this translation helpful? Give feedback.
All reactions