You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2012/12/01 15:17:58 UTC
[jira] [Created] (HDFS-4255) Useless stacktrace shown in DN when
there's an error writing a block
Harsh J created HDFS-4255:
-----------------------------
Summary: Useless stacktrace shown in DN when there's an error writing a block
Key: HDFS-4255
URL: https://issues.apache.org/jira/browse/HDFS-4255
Project: Hadoop HDFS
Issue Type: Improvement
Components: datanode
Affects Versions: 2.0.2-alpha
Reporter: Harsh J
Priority: Minor
The DN sometimes carries these, especially when its asked to shutdown and there's ongoing write activity. The stacktrace is absolutely useless and may be improved, and the message it comes as part of is an INFO, which should not be the case when a stacktrace is necessary to be print (indicative of a trouble).
{code}
2012-12-01 19:10:23,167 INFO datanode.DataNode (BlockReceiver.java:run(955)) - PacketResponder: BP-1493454111-192.168.2.1-1354369220726:blk_-8775461920430955284_1002, type=HAS_DOWNSTREAM_IN_PIPELINE
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.protocol.datatransfer.PipelineAck.readFields(PipelineAck.java:116)
at org.apache.hadoop.hdfs.server.datanode.BlockReceiver$PacketResponder.run(BlockReceiver.java:905)
at java.lang.Thread.run(Thread.java:680)
{code}
Full scenario log in comments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira