hangc0276 commented on PR #3205: URL: https://github.com/apache/bookkeeper/pull/3205#issuecomment-1098624372
> Looks like it's expected behavior? We have another configuration `isForceGCAllowWhenNoSpace` which is used to control the force gc is allowed when no space, maybe you need to set it to true? @zymap If we set `isForceGCAllowWhenNoSpace` to `true`, it won't suspend minor and major compaction on GC, which will easily lead to ledger disk space exhaustion. After we delete topic or shorten the retention to release disk space, we can't trigger compaction due to compaction need another disk space and the current disk space has been exhausted. So we are not recommend to set `isForceGCAllowWhenNoSpace` to `true` What we need is that the bookie suspend the minor and major compaction when disk usage reaches max threshold, but when we deleted topic or shorten the retention, we trigger GC by rest api, and bookie server neglect the current `suspendMajor` and `suspendMinor` flag to trigger compaction. -- 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]
