priyeshkaratha commented on PR #10775: URL: https://github.com/apache/ozone/pull/10775#issuecomment-5030712372
> I don't see any real use case for this feature. The doc citations are vague and do not correspond to any concrete actions an admin can take on an Ozone cluster. @priyeshkaratha if this was AI generated please do a more thorough review before requesting the community's time on this. > > > Operators regularly need a maintenance window in which SCM accepts reads but rejects writes — for example while performing disaster-recovery steps, inspecting or repairing state, coordinating an external migration, or draining activity before a controlled change. Restarting SCM to obtain this state is disruptive (it triggers re-registration and re-validation of all startup rules) and is not a per-node operation. SCM Manual Safe Mode is proposed to provide functionality similar to HDFS, where administrators can manually place the system into Safe Mode using the CLI. In HDFS, this capability is commonly used during maintenance activities to prevent changes to the file system while administrative operations are in progress. The same capability is being proposed for Ozone. I have updated the doc -- 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]
