[
https://issues.apache.org/jira/browse/HDFS-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029107#comment-13029107
]
Todd Lipcon commented on HDFS-1792:
-----------------------------------
Thanks for the feedback. I made the rename like you suggested. Please see
HDFS-1892, which is a related JIRA that takes into account the OP_INVALID based
filler.
> 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
