jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (OAK-7852) Blocked background flush can cause sever data loss
Date Wed, 24 Oct 2018 08:28:00 GMT

     [ https://issues.apache.org/jira/browse/OAK-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Michael Dürig resolved OAK-7852.
       Resolution: Won't Fix
    Fix Version/s:     (was: 1.10)

Resolving as won't fix for now:

All potential approaches for this issue have in common that they react to an unexpected failure
that should not happen in the first place (a stalled flush thread). Whatever we do at this
point, the system is already in a failed state and we don't want to make matters worse. We
should instead concentrate on detecting this situation and identify and fix the root cause
if it happens again. This is covered by OAK-7854 and external monitoring.


> Blocked background flush can cause sever data loss 
> ---------------------------------------------------
>                 Key: OAK-7852
>                 URL: https://issues.apache.org/jira/browse/OAK-7852
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>            Priority: Major
> When the {{FileStore background task}} fails (e.g. because of a deadlock) and the {{FileStore}}
is subsequently shutdown in an unclean way ({{kill -9}}) then there is a risk of a sever data
loss. Although a journal could be reconstructed from the segments, there is a chance that
most if not all of the revisions written since the failure of the background tasks are inconsistent
with a {{SNFE}}. 
> The expectation for such a case should be that a journal could be reconstructed from
the segments and that all but the last few revisions are consistent.

This message was sent by Atlassian JIRA

View raw message