ashishkumar50 commented on PR #11571: URL: https://github.com/apache/ozone/pull/11571#issuecomment-6341889992
@hani-fouladgar I have few questions regarding this change: > This PR adds a feedback loop so OM throttles its block-deletion load to SCM when SCM followers are highly lagged: - If throttle in SCM that means deletes will keep accumulating in OM if follower SCM remains slow due to some problem. And this can cause OM DB to bloat up. (Eg: If directory is deleted having millions of keys, directorydeletingservice will keep generating lot of deletedkeys in OM db but OM cannot send deleted keys to SCM which can cause OM db to grow) - Why throttle only block deletion and why not any other operation that also need ratis sync in SCM? - If follower has lagged by high margin it should do auto bootstrap? -- 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]
