hanishakoneru opened a new pull request #2491: URL: https://github.com/apache/ozone/pull/2491
## What changes were proposed in this pull request? 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. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-5534 ## How was this patch tested? Will add unit tests -- 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]
