You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2017/02/08 10:43:41 UTC

[jira] [Commented] (OAK-5602) avoid missing journal entries

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

Stefan Egli commented on OAK-5602:
----------------------------------

Note that OAK-5601 happened with a branch commit - which is trickier to handle: consider the extreme situation where a transaction is very long running (eg 12 hours) and also big enough to trigger branch purges/commits. Once such a session is saved the oldest of its branch commits can already be purged if we're only looking at normal commits and how far behind the backgroundRead is.

> avoid missing journal entries
> -----------------------------
>
>                 Key: OAK-5602
>                 URL: https://issues.apache.org/jira/browse/OAK-5602
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.6.0
>            Reporter: Stefan Egli
>             Fix For: 1.7.0, 1.8
>
>
> As a follow up of OAK-5601: that one is about a situation where backgroundRead falls way behind and journal GC cleans up journal entries before it was able to read it. We should generally look into improving this situation, eg by having journal GC not do the clean up as long as there are instances that haven't read the entry. This could perhaps be achieved by periodically having each instance inform the rest about what journal entries it has processed (or simpler: how far back it would be -find- fine for journal entries to be GC'ed)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)