[jira] [Commented] (BOOKKEEPER-949) Allow entryLog creation even when bookie is in RO mode for compaction

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838421#comment-15838421 ] 

ASF GitHub Bot commented on BOOKKEEPER-949:
-------------------------------------------

Github user reddycharan commented on the issue:

    https://github.com/apache/bookkeeper/pull/99
  
    ping..


> Allow entryLog creation even when bookie is in RO mode for compaction
> ---------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-949
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-949
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: bookkeeper-server
>    Affects Versions: 4.3.2
>            Reporter: Venkateswararao Jujjuri (JV)
>            Assignee: Venkateswararao Jujjuri (JV)
>            Priority: Critical
>
> When storage usage goes above threshold, there won't be any writable ledger dirs available and bookie turns RO. There can be multiple ways bookie can start compaction including isForceGCAllowWhenNoSpace enabled or by other means. When this happens the compaction process need to create a new entrylog to make progress on compaction. Creation of entrylog will fail because there are no writable ledger dirs.
> This is to allow entrylog creation if there is enough disk space even though used space is above threshold. Because after compaction space will stay the same or go below the threshold.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)