jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Dulceanu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4103) Replace journal.log with an in place journal
Date Mon, 11 Jul 2016 12:08:11 GMT

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

Andrei Dulceanu commented on OAK-4103:
--------------------------------------

[~frm] I'd like to work on this issue. Can you please assign it to me?

> Replace journal.log with an in place journal
> --------------------------------------------
>
>                 Key: OAK-4103
>                 URL: https://issues.apache.org/jira/browse/OAK-4103
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Priority: Minor
>              Labels: resilience
>             Fix For: 1.6, Segment Tar 0.0.4
>
>
> Instead of writing the current head revision to the {{journal.log}} file we could make
it an integral part of the node states: as OAK-3804 demonstrates we already have very good
heuristics to reconstruct a lost journal. If we add the right annotations to the root node
states this could replace the current approach. The latter is problematic as it relies on
the flush thread properly and timely updating {{journal.log}}. See e.g. OAK-3303. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message