[
https://issues.apache.org/jira/browse/BOOKKEEPER-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336757#comment-14336757
]
Flavio Junqueira commented on BOOKKEEPER-836:
---------------------------------------------
[~hustlmsp], I'm a bit confused about what the path is when the disk gets full.
If the disk is dedicated to the bookie, then it is full because of ledger data.
How do we reclaim disk space back in the case the disk gets full? Turning off
the compaction will slow down the process of getting the disk full, but I'm
worried about reclaiming space back.
> disable compaction when disk becomes full, otherwise compaction will fill up
> disk quickly
> -----------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-836
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-836
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server
> Affects Versions: 4.2.3
> Reporter: Jia Zhai
> Assignee: Jia Zhai
> Fix For: 4.4.0, 4.3.2
>
> Attachments: BOOKKEEPER-836-v2.patch, BOOKKEEPER-836.patch
>
>
> In doCompactEntryLogs, Entries are added to new logs, while all old logs were
> not released until the end of handling. So during the process, a lot of
> space will be used. Need to disable compaction when disk becomes full,
> otherwise compaction will fill up disk quickly.
> I would like to change old "forced garbage collection" logic, and suspend
> major compaction when it reaches warn threshold, suspend minor compaction
> when it reaches critical threshold.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
