[
https://issues.apache.org/jira/browse/HDFS-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026073#comment-13026073
]
Aaron T. Myers commented on HDFS-1792:
--------------------------------------
If the proposed change in HDFS-1846 gets checked in before this branch gets
merged, you'll need to make a change here. That said, the code can be
guaranteed to work, since the edits log will be guaranteed to end with 0xFFs
instead of maybe being filled with 0x00s.
> 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
