You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/09/10 09:40:46 UTC

[jira] [Commented] (OAK-2879) Compaction should check for required disk space before running

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

Michael Dürig commented on OAK-2879:
------------------------------------

Instead of checking disk space *before* running compaction a better solution would be to monitor disk space *during* compaction. Once it drops below a certain threshold, bail out and log. The extra segments introduced by the aborted compaction run will then get collected by the subsequent cleanup run. 

[~frm] assigning to you as discussed. 

> Compaction should check for required disk space before running
> --------------------------------------------------------------
>
>                 Key: OAK-2879
>                 URL: https://issues.apache.org/jira/browse/OAK-2879
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: segmentmk
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: compaction, doc-impacting, gc, resilience
>             Fix For: 1.3.7
>
>
> In the worst case compaction doubles the repository size while running. As this is somewhat unexpected we should check whether there is enough free disk space before running compaction and log a warning otherwise. This is to avoid a common source of running out of disk space and ending up with a corrupted repository. 



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