[jira] [Created] (HDDS-5534) Verify config is updated on all OMs before proceeding with Bootstrap

["Hanisha Koneru (Jira)" <ji...@apache.org>]

Hanisha Koneru created HDDS-5534:
------------------------------------

             Summary: Verify config is updated on all OMs before proceeding with Bootstrap
                 Key: HDDS-5534
                 URL: https://issues.apache.org/jira/browse/HDDS-5534
             Project: Apache Ozone
          Issue Type: Sub-task
            Reporter: Hanisha Koneru


When an OM is bootstrapped, it sends a SetConfiguration ratis request to leader OM and this request is propagated to all existing OMs in the ring. Existing OMs add the new OM to their peer list by reloading the config files and getting the new node information from the reloaded config files. But if the config file (ozone-site.xml) has not been updated on any OM, then that OM would crash when processing the SetConfiguration request. 

To avoid this scenario, before a bootstrap request is sent to the leader OM, the bootstrapping OM must verify that all the existing OMs have its information in their ozone-site.xml. To achieve this, we have added a new OMMetadata protocol. This protocol would be called during OM decommissioning also to verify that ozone-site.xmls are updated.

It could happen that an OM is down or not responding to a bootstrapping OMs metadata information call. In this scenario, to proceed with bootstrap, a "force" option is provided. During force bootstrap, the check for config update on existing OMs will be skipped.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org