You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Michael Bieniosek (JIRA)" <ji...@apache.org> on 2008/03/06 22:10:59 UTC

[jira] Created: (HADOOP-2957) DFSClient: All datanodes are bad

DFSClient: All datanodes are bad
--------------------------------

                 Key: HADOOP-2957
                 URL: https://issues.apache.org/jira/browse/HADOOP-2957
             Project: Hadoop Core
          Issue Type: Bug
          Components: dfs
    Affects Versions: 0.16.0
            Reporter: Michael Bieniosek


I got this extremely unhelpful error message: 

java.io.IOException: All datanodes x.x.x.x:50010 are bad. Aborting...
        at org.apache.hadoop.dfs.DFSClient$DFSOutputStream.processDatanodeError(DFSClient.java:1839)
        at org.apache.hadoop.dfs.DFSClient$DFSOutputStream.access$1100(DFSClient.java:1479)
        at org.apache.hadoop.dfs.DFSClient$DFSOutputStream$DataStreamer.run(DFSClient.java:1571)

In the code I note that there are several places in DFSClient where hasError is set to true.  Instead, there should be a message corresponding to hasError that gets set on the exception.  At very least, the exception should provide information about the bad block and indicate what sort of operation it was attempting.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.