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

Posted to issues@kudu.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2016/04/22 17:26:13 UTC

[jira] [Resolved] (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:all-tabpanel ]

Jean-Daniel Cryans resolved KUDU-1377.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9.0

Fixed in a series of patches, ending with bde7294fc0b0f9423a77c88c51ffa5e7915017ac.

> 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
>             Fix For: 0.9.0
>
>
> 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)