hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1630) Checksum fsedits
Date Fri, 18 Feb 2011 18:33:38 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996554#comment-12996554

Hairong Kuang commented on HDFS-1630:

Thank all for your inputs. I am thinking to use the pure Java CRC32 implemented in HADOOP-6148
to get the performance benefit. Checksum will be calculated and verified per transaction level.
This is because NN may get shutdown any time. So having a checksum per file level does not
work well.

@Steve, I will focus adding checksum to fsedit in this jira and then work on handling corrupt
fsedits in a different jira. I think Chansler opened a jira for handling corrupt fsedits in
SNN a while ago. Does this sound good to you?

> Checksum fsedits
> ----------------
>                 Key: HDFS-1630
>                 URL: https://issues.apache.org/jira/browse/HDFS-1630
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
> HDFS-903 calculates a MD5 checksum to a saved image, so that we could verify the integrity
of the image at the loading time.
> The other half of the story is how to verify fsedits. Similarly we could use the checksum
approach. But since a fsedit file is growing constantly, a checksum per file does not work.
I am thinking to add a checksum per transaction. Is it doable or too expensive?

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


View raw message