hangc0276 commented on PR #4555: URL: https://github.com/apache/bookkeeper/pull/4555#issuecomment-2687063261
> I believe this issue is related to optimization #3653. > > When using `deleteRange` to replace the one-by-one deletion method, only one action is written to RocksDB. If RocksDB is performing tiered compaction, this action is not guaranteed to be picked up, causing SST files to remain undeleted. > > To resolve this issue: Option 1: Revert to the previous logic of iteratively deleting each key. Option 2: Use compactRange to forcefully clean up levels L0 to L6. I chose to perform a compactRange synchronously when executing a major compaction. @danpi I think it should be a bug in RocksDB. We can use option 2 -- 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]
