sumitagrawl opened a new pull request, #9671: URL: https://github.com/apache/ozone/pull/9671
## What changes were proposed in this pull request? Exit of safemode status for follower when all rules are satisfied. This is as: - For leader applyTransaction completion is implicit before being choosen as leader. - For follower, exit safe mode rule as transaction sync and apply transaction keeps happening from leader node. This change in reference to below point in JIRA HDDS-5263: `But once the SCM Ratis server started it will replay logs from Transactioninfo last applied Index, so after that I see all pipelines are removed. (might be due to close pipeline)` So this have no issue for leader node once choosen during leader election. And for follower node, no need follow same restriction as dynamically the pipeline can be closed on runtime and same can be created by leader continuously. This check is present during startup to ensure SCM is writable and allow time to create pipeline as best effort and its not true always for the case of pipeline closure later on due to system unhealthy or other reason (System never moves back to Safemode later on as current behavior for any dynamic change later on). ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-14070 ## How was this patch tested? - impact of existing test case -- 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]
