[jira] [Updated] (BOOKKEEPER-662) Major GC should kick in immediately if remaining space reaches a warning threshold

["Ivan Kelly (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Kelly updated BOOKKEEPER-662:
----------------------------------

    Attachment: 0001-WIP.patch

This needs a rebase. I started but then came across a conflict with BOOKKEEPER-686. The problem is that when we're starting, we check all directories so that only those with enough space are selected for replaying the journal. I can't decide whether a disk at DiskWarnThreshold should be considered as having enough space or not. 

> Major GC should kick in immediately if remaining space reaches a warning threshold
> ----------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-662
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-662
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-server
>            Reporter: Sijie Guo
>            Assignee: Aniruddha
>             Fix For: 4.3.0
>
>         Attachments: 0001-WIP.patch, BOOKKEEPER-662.diff
>
>
> in a high throughput case, Major GC should kick in immediately if remaining spaces reaches a warning threshold.



--
This message was sent by Atlassian JIRA
(v6.1#6144)