[
https://issues.apache.org/jira/browse/OAK-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426519#comment-15426519
]
Andrei Dulceanu commented on OAK-4138:
--------------------------------------
Not sure I understood the comment inside {{FileStore.flush}}: "Decouple
revision cleanup from the flush thread: instead of synchronising, skip flush if
already in progress". My take on this one would be to move the cleanup in a
separate thread through another {{PeriodicOperation}}. [~mduerig] WDYT?
//cc [~alexparvulescu]
> Decouple revision cleanup from the flush thread
> -----------------------------------------------
>
> Key: OAK-4138
> URL: https://issues.apache.org/jira/browse/OAK-4138
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Andrei Dulceanu
> Labels: resilience
> Fix For: Segment Tar 0.0.12
>
>
> I suggest we decouple revision cleanup from the flush thread. With large
> repositories where cleanup can take several minutes to complete it blocks the
> flush thread from updating the journal and the persisted head thus resulting
> in larger then necessary data loss in case of a crash.
> /cc [~alex.parvulescu]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
