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] [Resolved] (HDFS-1792) Add code to detect valid length of an edits file
Date Thu, 31 Mar 2011 01:55:05 GMT

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

Todd Lipcon resolved HDFS-1792.
-------------------------------

    Resolution: Fixed

I've committed this to the edit log branch under the modified CTR policy on that branch. Please
feel free to re-open or open a new JIRA if you have review comments.

> 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
>    Affects Versions: Edit log branch (HDFS-1073)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: Edit log branch (HDFS-1073)
>
>         Attachments: hdfs-1792.txt
>
>
> 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