You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Venkateswararao Jujjuri (JV) (JIRA)" <ji...@apache.org> on 2016/09/28 16:28:20 UTC
[jira] [Created] (BOOKKEEPER-949) Allow entryLog creation even when
bookie is in RO mode for compaction
Venkateswararao Jujjuri (JV) created BOOKKEEPER-949:
-------------------------------------------------------
Summary: 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)