jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-5602) Avoid missing journal entries
Date Tue, 25 Jul 2017 09:57:00 GMT

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

Marcel Reutegger commented on OAK-5602:
---------------------------------------

Added an ignored test to trunk that shows the effect of a long running transaction on the
DocumentNodeStore node state diff mechanism: http://svn.apache.org/r1802910

> 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
>            Assignee: Marcel Reutegger
>             Fix For: 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.4.14#64029)

Mime
View raw message