[
https://issues.apache.org/jira/browse/OAK-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding updated OAK-6052:
--------------------------------
Attachment: OAK-6052-reader-iterable.patch
Thanks for the explanation regarding the interplay of locking readers and the
writer. Could you please add this to the javadoc as well? I think it's helpful.
Attached is a patch implementing the proposal with the {{Iterable<TarReader}}.
[~frm] please take a look an apply if you're happy with this. I'm not 100%
confident I maintained all invariants.
> 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.7.0, 1.8
>
> Attachments: OAK-6052-reader-iterable.patch
>
>
> 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)
