ivandika3 opened a new pull request, #9385: URL: https://github.com/apache/ozone/pull/9385
## What changes were proposed in this pull request? Currently if we would like to migrate the SCM from (scm1, scm2, scm3) to (scm4, scm5, scm6), all the datanodes need to be restarted 2 times with updated "ozone.scm.nodes.<service>" configuration Before migration: Update ozone.scm.nodes to (scm1, scm2, scm3, scm4, scm5, scm6) After (scm1, scm2, scm3) are decommissioned: Update ozone.scm.nodes to (scm4, scm5, scm6) As mentioned in [HDDS-12391](https://issues.apache.org/jira/browse/HDDS-12391), rolling restarting all the datanodes might take a while. For large datanodes fleet this might take a lot of time (days or even weeks). It might be good to support dynamic reconfiguration of SCM endpoints in DN to prevent restarts. A possible flow Admin update the "ozone.scm.nodes" to the new value (with some new nodes and removed nodes) DN will compare the new and previous configuration and find the SCM endpoints to add and remove DN will add the SCM endpoints (e.g. SCMConnectionManager#addSCMServer) and then remove the SCM endpoints (e.g. SCMConnectionManager#removeSCMServer). ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-13890 ## How was this patch tested? Integration test. -- 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]
