sumitagrawl commented on PR #7177: URL: https://github.com/apache/ozone/pull/7177#issuecomment-2342823139
> I agree with @errose28 on this. Opening up a way to modify the db directly without any restriction is not a good idea. It's very hard to have unit/functional tests to cover all the scenarios. We could end up in a situation where we won't even know how the data in the db got corrupted. > > If it's must, it is better to have specific tool or repair command to fix the problem which users frequently run into. To handle same, 1. proto validation is used to validate data (basic one) 2. we are planning add audit log to record all changes done in DB itself (diff of changes if exist, new add record, or delete data) - [HDDS-11447](https://issues.apache.org/jira/browse/HDDS-11447) The audit generally is not there in other repair command using tool, but this as unified approach for tracking changes via this will help in recording changes. This can remove the risk of corrupt and tracking and recovering on need basis. But as support, instead of downloading `rosckdb ldb tool `and using same is having `higher risk` as done for immediate recovery of environment and may not be possible for certain cases. -- 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]
