This is an automated email from the ASF dual-hosted git repository.
adoroszlai pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone.git
The following commit(s) were added to refs/heads/master by this push:
new 7127355073 HDDS-9409. Update SCM decommissioning documentation. (#5418)
7127355073 is described below
commit 7127355073486544d9d52aaddedd98a03a32259c
Author: Nandakumar Vadivelu <[email protected]>
AuthorDate: Sat Oct 21 00:53:44 2023 +0530
HDDS-9409. Update SCM decommissioning documentation. (#5418)
---
hadoop-hdds/docs/content/feature/Decommission.md | 23 ++++++++++++++++-------
1 file changed, 16 insertions(+), 7 deletions(-)
diff --git a/hadoop-hdds/docs/content/feature/Decommission.md
b/hadoop-hdds/docs/content/feature/Decommission.md
index bc8bc6805b..86a345a460 100644
--- a/hadoop-hdds/docs/content/feature/Decommission.md
+++ b/hadoop-hdds/docs/content/feature/Decommission.md
@@ -23,7 +23,7 @@ summary: Decommissioning of SCM, OM and Datanode.
limitations under the License.
-->
-#DataNode Decommission
+# DataNode Decommission
The DataNode decommission is the process that removes the existing DataNode
from the Ozone cluster while ensuring that the new data should not be written
to the decommissioned DataNode. When you initiate the process of
decommissioning a DataNode, Ozone automatically ensures that all the storage
containers on that DataNode have an additional copy created on another DataNode
before the decommission completes. So, datanode will keep running after it has
been decommissioned and may be used f [...]
@@ -57,7 +57,7 @@ ozone admin datanode recommission [-hV] [-id=<scmServiceId>]
[--scm=<scm>] [<hosts>...]
```
-## OM Decommission
+# OM Decommission
Ozone Manager (OM) decommissioning is the process in which you gracefully
remove one of the OM from the OM HA Ring.
@@ -77,15 +77,24 @@ Storage Container Manager (SCM) decommissioning is the
process in which you can
To decommission a SCM and remove the node from the SCM HA ring, the following
steps need to be executed.
```shell
-ozone admin scm decommission [-hV] [-id=<scmServiceId>] -nodeid=<nodeId>
- [--scm=<scm>]
+ozone admin scm decommission [-hV] [--service-id=<scmServiceId>]
-nodeid=<nodeId>
```
You can obtain the 'nodeId' by executing this command, **"ozone admin scm
roles"**
-**Note -** If you want to decommission a **primordial** scm, you may first
transfer the leadership to a non primordial scm and then decommission the
primordial scm.
+### Leader SCM
+If you want to decommission the **leader** scm, you must first transfer the
leadership to a different scm and then decommission the node.
To transfer the leader, we can excute below command,
```shell
-ozone admin scm transfer --service-id=scmservice -n ${nodeId}
+ozone admin scm transfer [--service-id=<scmServiceId>] -n=<nodeId>
```
-After successful leadership change we can follow the above decommissioning
command to decommission the scm node.
+After successful leadership change you can proceed with decommissioning.
+
+### Primordial SCM
+If you want to decommission the **primordial** scm, you have to change the
_ozone.scm.primordial.node.id_ property to point to a different SCM and then
proceed with decommissioning.
+
+
+### Note
+During SCM decommissioning the private key of the decommissioned SCM should be
manually deleted. The private keys can be found inside _hdds.metadata.dir_.
+
+Manual deletion is needed until we have certificate revocation support
(HDDS-8399)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
