captainzmc commented on PR #3286: URL: https://github.com/apache/ozone/pull/3286#issuecomment-1100033309
Thank @errose28 and @sodonnel for your feedback. I get your point. > It still does not prevent someone (or a bad application) writing keys up to the quota, and then abandoning them, filling up the system. > > Perhaps we need some sort of "open key + abandoned key" quota to go along with the committed quota. But that starts to make it harder to understand how the whole system works, which is bad for users too! Agree. At allocate time check quota, failed keys are treated as part of the system. This will not guarantee a user could fill up the system by writing some failed key. Ozone's current implementation has none of these risks. However, it does not solve the problems encountered by the Clean Open Key Service. I have an idea here. Currently, all keys need to be delete before Ozone deletes a bucket. In fact, this part of the key need contain the Open key? If yes, can we implement an interface that allows users to clean the Open key under a bucket? Just my idea, and if there's some other way, I'm glad to discuss. cc @errose28 @sodonnel -- 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]
