Hi Chris,
I did as what you said to remove the peer but still got the dead node show up. Anything I missed to get it removed please?
Here is the steps I used for testing:
1. starting 4 master nodes on 3 virtual machines which were working fine as below
10.12.6.11
weed master -mdir=/home/seaweedfs/seaweedfs/mdata -ip=10.12.6.11 -ip.bind=10.12.6.11 -port=9333 -peers=
10.12.6.11:9333,
10.12.6.12:9333,
10.12.6.13:9333,
10.12.6.13:9334 -defaultReplication=110
10.12.6.12
weed master -mdir=/home/seaweedfs/seaweedfs/mdata -ip=10.12.6.12 -ip.bind=10.12.6.12 -port=9333 -peers=
10.12.6.11:9333,
10.12.6.12:9333,
10.12.6.13:9333,
10.12.6.13:9334 -defaultReplication=110
10.12.6.13
weed master -mdir=/home/seaweedfs/seaweedfs/mdata -ip=10.12.6.13 -ip.bind=10.12.6.13 -port=9333 -peers=
10.12.6.11:9333,
10.12.6.12:9333,
10.12.6.13:9333,
10.12.6.13:9334 -defaultReplication=110
weed master -mdir=/home/seaweedfs/seaweedfs/mdata_9334 -ip=10.12.6.13 -ip.bind=10.12.6.13 -port=9334 -peers=
10.12.6.11:9333,
10.12.6.12:9333,
10.12.6.13:9333,
10.12.6.13:9334 -defaultReplication=110
2. stop all masters and remove the directory mdata_9334 in 10.12.6.13
3. restart the rest 3 masters, I still could see
10.12.6.13:9334 existing in peers...
Btw, I checked all conf file in the folder where mdir points to, all are still showing as this:{"commitIndex":109,"peers":[{"name":"
10.12.6.12:9333","connectionString":"
http://10.12.6.12:9333"},{"name":"
10.12.6.11:9333","connectionString":"
http://10.12.6.11:9333"},{"name":"
10.12.6.13:9334","connectionString":"
http://10.12.6.13:9334"}]}.
So I
Thanks,
Joe
在 2017年4月11日星期二 UTC+8上午2:45:10,ChrisLu写道: