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

Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2016/03/21 23:16:25 UTC

[jira] [Commented] (KUDU-1377) Log block manager metadata doesn't handle partial truncation

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

Adar Dembo commented on KUDU-1377:
----------------------------------

Probably not an outright dupe of KUDU-668 but certainly worth reading that bug for more context.

> Log block manager metadata doesn't handle partial truncation
> ------------------------------------------------------------
>
>                 Key: KUDU-1377
>                 URL: https://issues.apache.org/jira/browse/KUDU-1377
>             Project: Kudu
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.7.1
>            Reporter: Mike Percy
>            Assignee: Mike Percy
>
> If the log block manager's metadata file gets only partially written, this will result in failure to start up again. Since we are constantly appending, this is a problem since partial writes can occur when the disk fills up (among other potential error conditions like a system crash during a write).
> Pointer to the code in question: https://github.com/apache/incubator-kudu/blob/0.7.1/src/kudu/fs/log_block_manager.cc#L437



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