[
https://issues.apache.org/jira/browse/HDFS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862348#action_12862348
]
sam rash commented on HDFS-1122:
--------------------------------
This results in these log messages:
2010-04-21 13:06:30,951 WARN
org.apache.hadoop.hdfs.server.datanode.DataBlockScanner: Adding an already
existing block blk_6423942125821562308_117574
2010-04-21 12:59:47,054 WARN
org.apache.hadoop.hdfs.server.datanode.DataBlockScanner: Adding an already
existing block blk_-1890060265487773738_117566
2010-04-21 12:56:26,831 WARN
org.apache.hadoop.hdfs.server.datanode.DataBlockScanner: Adding an already
existing block blk_-8254097362836825914_117561
2010-04-21 12:53:03,386 WARN
org.apache.hadoop.hdfs.server.datanode.DataBlockScanner: Adding an already
existing block blk_8946894423251690136_117557
2010-04-21 12:49:43,148 WARN
org.apache.hadoop.hdfs.server.datanode.DataBlockScanner: Adding an already
existing block blk_-5467425469535997066_117553
2010-04-21 12:46:22,613 WARN
org.apache.hadoop.hdfs.server.datanode.DataBlockScanner: Adding an already
existing block blk_-3020378094937646676_117549
and its possible the block scanner could mark the blocks corrupt since they are
being written to. I have a test + 0.20 patch I will upload shortly (crux of
patch is that client verifications can only update the DataBlockScanner, not
add new blocks).
> client block verification may result in blocks in DataBlockScanner prematurely
> ------------------------------------------------------------------------------
>
> Key: HDFS-1122
> URL: https://issues.apache.org/jira/browse/HDFS-1122
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: sam rash
> Assignee: sam rash
>
> found that when the DN uses client verification of a block that is open for
> writing, it will add it to the DataBlockScanner prematurely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
