Harsh J created HDFS-7899:
-----------------------------
Summary: 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
Priority: Minor
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)
