Thanks @Shashikant Banerjee <sbaner...@cloudera.com> for bringing this up. +1 for the merging proposal, which will also help 1. Earlier deployment and feedback. 2. Help branch work that has dependency OM HA.
Having a switch to disable the feature by default is good. But still, we want to have clear document on 1. how to start a fresh HA enabled SCM cluster. 2. how to bootstrap a standalone SCM cluster to HA enabled. Regards, Xiaoyu On Mon, Mar 8, 2021 at 10:51 AM Shashikant Banerjee <sbaner...@cloudera.com.invalid> wrote: > Hi All, > > I would like to start a discussion thread regarding the SCM HA feature ( > https://issues.apache.org/jira/browse/HDDS-2823) and it's merge back to > the > ozone master branch in the ozone community. > > As currently, SCM is a single point of failure for the Ozone and SCM HA > support is proposed to resolve the ultimate need for Ozone HA after OM HA > has already been made available. > > The feature work is functionally complete now with SCM HA security work > already in progress. There is a config to turn the HA feature on and off > and while merging back to master , it will be turned off by default for > now. > > Merging back to master will help in stabilizing/testing the feature more > rigorously while ensuring the ongoing work on the master branch is not > negatively impacted by the feature by ensuring that the feature is turned > off by default. > > Thanks > Shashi >
