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 "Julian Reschke (JIRA)" <ji...@apache.org> on 2016/02/17 12:24:18 UTC

[jira] [Comment Edited] (OAK-4022) DocumentNodeStoreService journal write should log write failures

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

Julian Reschke edited comment on OAK-4022 at 2/17/16 11:24 AM:
---------------------------------------------------------------

trunk: http://svn.apache.org/r1730801
1.2: http://svn.apache.org/r1730812
1.0: http://svn.apache.org/r1730816



was (Author: reschke):
trunk: http://svn.apache.org/r1730801


> DocumentNodeStoreService journal write should log write failures
> ----------------------------------------------------------------
>
>                 Key: OAK-4022
>                 URL: https://issues.apache.org/jira/browse/OAK-4022
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>    Affects Versions: 1.2.11, 1.3.15, 1.0.27
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: 1.2.12, 1.0.28, 1.3.17
>
>         Attachments: OAK-4022.diff
>
>
> Currently, {{DocumentNodeStore.backgroundWrite()}} will handle failures to create a journal entry silently, just accumulating the changes. If the {{DocumentStore}} implementation consistently fails to create new entries, the changes document will essentially grow indefinitely.
> Minimally, the code should log an error when then journal entry could not be written; allowing the problem to be further analyzed.



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