/agent/leave, /catalog/deregister, and a few other things, to no avail. How do I keep one Consul Cluster KV store and Consul Leader from overwriting the Consul Leader & KV store of another Consul Cluster?
Consul parting is such sweet sorrow,
--Nathan Basanese
P.S. I posted about it here:
https://serverfault.com/questions/852520/how-do-i-completely-remove-a-node-from-a-consul-cluster
But maybe it's better to discuss this sort of issue in the Consul mailing list than a Q&A site.
nathan-basanese-zsh8@prd0consulserver3 ~]$ consul operator raft list-peers192.176.100.3:8300 192.176.100.3:8300 follower true <=1192.176.100.2:8300 192.176.100.2:8300 follower true <=1nathan-basanese-zsh8@prd0consulserver3 ~]$ consul operator raft remove-peer 192.176.100.2:8300[nathan-basanese-zsh8@alpha0consulserver2.alpha0 ~]% consul operator raft list-peerscurl -s --upload-file /etc/consul.d/services.json http://127.0.0.1:8500/v1/agent/service/deregister/db-test
{ "services": [ { "name": "db-test", "tags": [ "writes", "reads" ], "port": 3306, "checks": [ { "script": "/etc/consul.d/scripts/mysql.sh", "interval": "5s" } ] } ]}
curl -s --upload-file /etc/consul.d/services.json http://127.0.0.1:8500/v1/agent/service/deregister/db-test
{ "services": [ { "name": "db-test", "tags": [ "writes", "reads" ], "port": 3306, "checks": [ { "script": "/etc/consul.d/scripts/mysql.sh", "interval": "5s" } ] } ]}