Merge pull request #47308 from lahinson/OSDOCS-3779-unhealthy-etcd

OSDOCS-3779 adding instructions to remove unhealthy etcd member

Author: mburke5678

modules/restore-replace-stopped-etcd-member.adoc

@@ -71,9 +71,43 @@ sh-4.2# etcdctl member list -w table
 +
 Take note of the ID and the name of the unhealthy etcd member, because these values are needed later in the procedure. The `$ etcdctl endpoint health` command will list the removed member until the procedure of replacement is finished and a new member is added.
 
+.. Remove the unhealthy etcd member by providing the ID to the `etcdctl member remove` command:
++
+[source,terminal]
+----
+sh-4.2# etcdctl member remove 6fc1e7c9db35841d
+----
++
+.Example output
+[source,terminal]
+----
+Member 6fc1e7c9db35841d removed from cluster ead669ce1fbfb346
+----
 
+.. View the member list again and verify that the member was removed:
++
+[source,terminal]
+----
+sh-4.2# etcdctl member list -w table
+----
++
+.Example output
+[source,terminal]
+----
++------------------+---------+------------------------------+---------------------------+---------------------------+
+|        ID        | STATUS  |             NAME             |        PEER ADDRS         |       CLIENT ADDRS        |
++------------------+---------+------------------------------+---------------------------+---------------------------+
+| 757b6793e2408b6c | started |  ip-10-0-164-97.ec2.internal |  https://10.0.164.97:2380 |  https://10.0.164.97:2379 |
+| ca8c2990a0aa29d1 | started | ip-10-0-154-204.ec2.internal | https://10.0.154.204:2380 | https://10.0.154.204:2379 |
++------------------+---------+------------------------------+---------------------------+---------------------------+
+----
 +
 You can now exit the node shell.
++
+[IMPORTANT]
+====
+After you remove the member, the cluster might be unreachable for a short time while the remaining etcd instances reboot.
+====
 
 . Remove the old secrets for the unhealthy etcd member that was removed.