hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1792) Add code to detect valid length of an edits file
Date Tue, 29 Mar 2011 06:34:05 GMT

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

Todd Lipcon updated HDFS-1792:
------------------------------

    Description: In some edit log corruption situations, it's useful to be able to determine
the "valid" length of an edit log. For this JIRA we define "valid" as the length of the file
excluding any trailing 0x00 bytes, usually left there by the preallocation done while writing.
In the future this API can be extended to look at edit checksums, etc.

> Add code to detect valid length of an edits file
> ------------------------------------------------
>
>                 Key: HDFS-1792
>                 URL: https://issues.apache.org/jira/browse/HDFS-1792
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>
> In some edit log corruption situations, it's useful to be able to determine the "valid"
length of an edit log. For this JIRA we define "valid" as the length of the file excluding
any trailing 0x00 bytes, usually left there by the preallocation done while writing. In the
future this API can be extended to look at edit checksums, etc.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message