ivandika3 commented on PR #10876: URL: https://github.com/apache/ozone/pull/10876#issuecomment-5100606685
> Is there some bulk delete in the buckets? We can do something similar for the delete as well and add delete range tombstone as well. @swamirishi Yes, we have the S3 lifecycle configuration service (HDDS-8342) that generates a few millions deletions in a very short time. In LEGACY bucket `getFileStatus` can trigger a RocksDB seek that is done under a bucket lock, if there are a lot of tombstones, then the lock will be held for a long time which can block Ratis applier and cause the OM write to be stuck. The lifecycle configuration service cannot use deleteRange (unlike DirectoryDeletingService) since another key can be created in the deleteRange which can cause valid keys to be inadvertently deleted. > Do you guys have ACL bloat problem? We previously had one, but we already resolved it so that now a single key usually only have 1 ACL only. Our custom authorizer allows us to have a stable ACL. But each OmKeyInfo can be large due to a lot of blocks (for example, if a key is uploaded using MPU with very small parts), so the risk is still there. -- 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]
