sarvekshayr commented on code in PR #221:
URL: https://github.com/apache/ozone-site/pull/221#discussion_r2665598475


##########
docs/05-administrator-guide/02-configuration/06-high-availability/01-scm-ha.md:
##########
@@ -0,0 +1,280 @@
+---
+sidebar_label: SCM HA Configuration
+---
+
+# SCM High Availability Configuration
+
+## Configuration
+
+One Ozone configuration (`ozone-site.xml`) can support multiple SCM HA node 
set, multiple Ozone clusters. To select between the available SCM nodes a 
logical name is required for each of the clusters which can be resolved to the 
IP addresses (and domain names) of the Storage Container Managers.
+
+This logical name is called `serviceId` and can be configured in the 
`ozone-site.xml`
+
+Most of the time you need to set only the values of your current cluster:
+
+```xml
+<property>
+   <name>ozone.scm.service.ids</name>
+   <value>cluster1</value>
+</property>
+```
+
+For each of the defined `serviceId` a logical configuration name should be 
defined for each of the servers
+
+```xml
+<property>
+   <name>ozone.scm.nodes.cluster1</name>
+   <value>scm1,scm2,scm3</value>
+</property>
+```
+
+The defined prefixes can be used to define the address of each of the SCM 
services:
+
+```xml
+<property>
+   <name>ozone.scm.address.cluster1.scm1</name>
+   <value>host1</value>
+</property>
+<property>
+   <name>ozone.scm.address.cluster1.scm2</name>
+   <value>host2</value>
+</property>
+<property>
+   <name>ozone.scm.address.cluster1.scm3</name>
+   <value>host3</value>
+</property>
+```
+
+For reliable HA support choose 3 independent nodes to form a quorum.
+
+## Bootstrap
+
+The initialization of the **first** SCM-HA node is the same as a non-HA SCM:
+
+```bash
+ozone scm --init
+```
+
+Second and third nodes should be *bootstrapped* instead of init. These 
clusters will join to the configured RAFT quorum. The id of the current server 
is identified by DNS name or can be set explicitly by `ozone.scm.node.id`. Most 
of the time you don't need to set it as DNS based id detection can work well.
+
+```bash
+ozone scm --bootstrap
+```
+
+Note: both commands perform one-time initialization.  SCM still needs to be 
started by running `ozone --daemon start scm`.
+
+## SCM Leader Transfer

Review Comment:
   `SCM Leader Transfer` is added in 
https://ozone-site-v2.staged.apache.org/docs/administrator-guide/operations/leader-transfer/storage-container-manager/.
 
   Link the doc here instead.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to