hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Gupta (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2263) Make DFSClient report bad blocks more quickly
Date Tue, 27 Sep 2011 19:55:45 GMT

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

Arpit Gupta commented on HDFS-2263:

Here is the output of the dfs -cat call where it reports the node as dead

Here is the output of the dfs -cat

11/09/27 18:06:05 WARN hdfs.DFSClient: Failed to connect to /IP:1019, add to deadNodes and
continuejava.io.IOException: Got error for OP_READ_BLOCK, self=/IP:55657, remote=/IP:1019,
for file /some_file.txt, for block -607102961416835735_7654

11/09/27 18:06:05 INFO hdfs.DFSClient: Could not obtain block blk_-607102961416835735_7654
from any node: java.io.IOException: No live nodes contain current block. Will get new block
locations from namenode and retry

at org.apache.hadoop.hdfs.DFSClient$DFSInputStream.chooseDataNode(DFSClient.java:2093)
at org.apache.hadoop.hdfs.DFSClient$DFSInputStream.blockSeekTo(DFSClient.java:1897)
at org.apache.hadoop.hdfs.DFSClient$DFSInputStream.read(DFSClient.java:2048)
at java.io.DataInputStream.read(DataInputStream.java:83)
at org.apache.hadoop.io.IOUtils.copyBytes(IOUtils.java:68)
at org.apache.hadoop.io.IOUtils.copyBytes(IOUtils.java:47)
at org.apache.hadoop.io.IOUtils.copyBytes(IOUtils.java:100)
at org.apache.hadoop.fs.FsShell.printToStdout(FsShell.java:114)
at org.apache.hadoop.fs.FsShell.access$100(FsShell.java:49)
at org.apache.hadoop.fs.FsShell$1.process(FsShell.java:349)
at org.apache.hadoop.fs.FsShell$DelayedExceptionThrowing.globAndProcess(FsShell.java:1913)
at org.apache.hadoop.fs.FsShell.cat(FsShell.java:346)
at org.apache.hadoop.fs.FsShell.doall(FsShell.java:1557)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:1776)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:79)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:1895)

And then after this if the fsck call is made it reports the fs as healthy. It should mark
the fs as corrupt.
> Make DFSClient report bad blocks more quickly
> ---------------------------------------------
>                 Key: HDFS-2263
>                 URL: https://issues.apache.org/jira/browse/HDFS-2263
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs client
>    Affects Versions: 0.20.2
>            Reporter: Aaron T. Myers
>            Assignee: Harsh J
> In certain circumstances the DFSClient may detect a block as being bad without reporting
it promptly to the NN.
> If when reading a file a client finds an invalid checksum of a block, it immediately
reports that bad block to the NN. If when serving up a block a DN finds a truncated block,
it reports this to the client, but the client merely adds that DN to the list of dead nodes
and moves on to trying another DN, without reporting this to the NN.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message