[
https://issues.apache.org/jira/browse/HDFS-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268970#comment-13268970
]
Hudson commented on HDFS-3357:
------------------------------
Integrated in Hadoop-Mapreduce-trunk #1070 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1070/])
HDFS-3357. DataXceiver reads from client socket with incorrect/no timeout.
Contributed by Todd Lipcon. (Revision 1334116)
Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1334116
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiverServer.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDataTransferKeepalive.java
> DataXceiver reads from client socket with incorrect/no timeout
> --------------------------------------------------------------
>
> Key: HDFS-3357
> URL: https://issues.apache.org/jira/browse/HDFS-3357
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node
> Affects Versions: 1.0.2, 2.0.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: hdfs-3357.txt, hdfs-3357.txt, hdfs-3357.txt
>
>
> In DataXceiver, we currently use Socket.setSoTimeout to try to manage the
> read timeout when switching between reading the initial opCode, reading a
> keepalive opcode, and reading the status after a successfully sent block.
> However, since all of these reads use the same underlying DataInputStream,
> the change to the socket timeout isn't respected. Thus, they all occur with
> whatever timeout is set on the socket at the time of DataXceiver
> construction. In practice this turns out to be 0, which can cause infinitely
> hung xceivers.
--
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
