jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-4015) Expedite commits from the compactor
Date Fri, 11 Mar 2016 09:43:06 GMT

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

Michael Dürig commented on OAK-4015:

Making OAK-3348 a blocker of this. As a fix to the former might introduce significant changes
I want to have a better grasp on how we go forward there until we take this one up.

> Expedite commits from the compactor
> -----------------------------------
>                 Key: OAK-4015
>                 URL: https://issues.apache.org/jira/browse/OAK-4015
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segmentmk
>            Reporter: Michael Dürig
>              Labels: compaction, gc, perfomance
>             Fix For: 1.6
>         Attachments: OAK-4015-histo.png, OAK-4015-wait-time.png
> Concurrent commits during compaction cause those to be re-compacted. Currently it seems
that the compaction thread can end up waiting for some time to acquire the commit lock [1],
which in turn causes more commits to pile up to be re-compacted. I think this could be improved
by tweaking the lock such that the compactor could jump ahead of the queue. I.e. use a lock
which can be acquired in expedited mode. 
> [1] SegmentNodeStore#commitSemaphore

This message was sent by Atlassian JIRA

View raw message