jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (OAK-3055) Improve segment cache in SegmentTracker
Date Wed, 22 Jul 2015 08:49:05 GMT

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

Alex Parvulescu edited comment on OAK-3055 at 7/22/15 8:48 AM:
---------------------------------------------------------------

bq. small performance improvement
[~tmueller] 1.3.3 is already out, please create a dedicated issue for this change with the
1.3.4 fix version


was (Author: alex.parvulescu):
bq. small performance improvement
Thomas Mueller 1.3.3 is already out, please create a dedicated issue for this change with
the 1.3.4 fix version

> Improve segment cache in SegmentTracker
> ---------------------------------------
>
>                 Key: OAK-3055
>                 URL: https://issues.apache.org/jira/browse/OAK-3055
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segmentmk
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: doc-impacting, resilience, scalability
>             Fix For: 1.3.3
>
>         Attachments: OAK-3055.patch
>
>
> The hand crafted segment cache in {{SegmentTracker}} is prone to lock contentions in
concurrent access scenarios. As {{SegmentNodeStore#merge}} might also end up acquiring this
lock while holding the commit semaphore the situation can easily lead to many threads being
blocked on the commit semaphore. The {{SegmentTracker}} cache doesn't differentiate between
read and write access, which means that reader threads can block writer threads. 



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

Mime
View raw message