hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7899) Improve EOF error message
Date Tue, 06 Oct 2015 13:19:27 GMT

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

Hudson commented on HDFS-7899:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #485 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/485/])
HDFS-7899. Improve EOF error message (Contributed by Jagadesh Kiran N) (vinayakumarb: rev
874c8ed2399ff5f760d358abae3e98c013f48d22)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/protocolPB/PBHelperClient.java


> Improve EOF error message
> -------------------------
>
>                 Key: HDFS-7899
>                 URL: https://issues.apache.org/jira/browse/HDFS-7899
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client
>    Affects Versions: 2.6.0
>            Reporter: Harsh J
>            Assignee: Jagadesh Kiran N
>            Priority: Minor
>             Fix For: 2.8.0
>
>         Attachments: HDFS-7899-00.patch, HDFS-7899-01.patch, HDFS-7899-02.patch
>
>
> Currently, a DN disconnection for reasons other than connection timeout or refused messages,
such as an EOF message as a result of rejection or other network fault, reports in this manner:
> {code}
> WARN org.apache.hadoop.hdfs.DFSClient: Failed to connect to /x.x.x.x:nnnn for block,
add to deadNodes and continue. java.io.EOFException: Premature EOF: no length prefix available

> java.io.EOFException: Premature EOF: no length prefix available 
> at org.apache.hadoop.hdfs.protocol.HdfsProtoUtil.vintPrefixed(HdfsProtoUtil.java:171)

> at org.apache.hadoop.hdfs.RemoteBlockReader2.newBlockReader(RemoteBlockReader2.java:392)

> at org.apache.hadoop.hdfs.BlockReaderFactory.newBlockReader(BlockReaderFactory.java:137)

> at org.apache.hadoop.hdfs.DFSInputStream.getBlockReader(DFSInputStream.java:1103) 
> at org.apache.hadoop.hdfs.DFSInputStream.blockSeekTo(DFSInputStream.java:538) 
> at org.apache.hadoop.hdfs.DFSInputStream.readWithStrategy(DFSInputStream.java:750) 
> at org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:794) 
> at org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:602) 
> {code}
> This is not very clear to a user (warn's at the hdfs-client). It could likely be improved
with a more diagnosable message, or at least the direct reason than an EOF.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message