[
https://issues.apache.org/jira/browse/OAK-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963004#comment-15963004
]
Francesco Mari commented on OAK-6052:
-------------------------------------
I reorganized the implementation of {{TarFiles}} at r1790844. TAR readers are
now organized in a linked list. The lock is held for the time necessary to read
or write the references to the the TAR writer or to the head of the linked list
containing the TAR readers. Most of the time, it's not necessary hold any lock
- e.g. while traversing the list of TAR readers. Moreover, the cleanup
operation has been refactored to a compare-and-set operation on the list of TAR
readers.
> Cleanup blocks writers
> ----------------------
>
> Key: OAK-6052
> URL: https://issues.apache.org/jira/browse/OAK-6052
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Francesco Mari
> Labels: cleanup, gc
> Fix For: 1.8, 1.7.4
>
>
> The refactoring from OAK-6002 moved the cleanup of the tar readers into the
> read lock, which blocks concurrent writers from progressing. This was a
> problem with {{oak-segment}} before and fixed with OAK-3329.
> As cleanup can take up to a couple of minutes on busy system we should
> re-establish the former behaviour.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
