bharatviswa504 commented on pull request #1083: URL: https://github.com/apache/hadoop-ozone/pull/1083#issuecomment-645697193
@maobaolong Thanks for the detailed explanation. HDDS-3668 is a workaround until upgrades are properly handled. Once upgrades are handled, then it will be the responsibility of the feature developer to handle such scenarios. This was discussed in detail in the section "Extending Layout Features for OM" Ya agree, for now, this has caused trouble for existing deployments. > even i can remove the rocksdb persistent file on the disk I don't think if someone goes to the metadata folder and deletes it directly, I am not sure there is no way to safeguard such a situation, and user is risking his data on the cluster. Because now we are exposing such a CLI tool to end-user, this seems risky. > so i think we should prevent anybody/user to do the risky operation to Ozone cluster, but we should let someone with high permission of the cluster like me can do something they know they can do safety, and they can be responsible for the risk by their operation. Do you think having an admin check here would safeguard any user from doing this? And also printing out some WARN message to let the user remind about the operation they are trying to perform here. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
