[
https://issues.apache.org/jira/browse/HDFS-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902449#action_12902449
]
Dmitry Musatov commented on HDFS-693:
-------------------------------------
Setting dfs.datanode.socket.write.timeout to zero decreases actual timeout both
for DFS Client and Server, but for Server it also switches from NIO to Regular
socket implementation.
Prooflink:
http://svn.apache.org/viewvc/hadoop/common/tags/release-0.20.2/src/hdfs/org/apache/hadoop/hdfs/server/datanode/DataNode.java?revision=916569&view=markup
Lines (250,251),(307,308),(403-407) or search for socketWriteTimeout
> java.net.SocketTimeoutException: 480000 millis timeout while waiting for
> channel to be ready for write exceptions were cast when trying to read file
> via StreamFile.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-693
> URL: https://issues.apache.org/jira/browse/HDFS-693
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node
> Affects Versions: 0.20.1
> Reporter: Yajun Dong
> Attachments: HDFS-693.log
>
>
> To exclude the case of network problem, I found the count of dataXceiver is
> about 30. Also, I could see the output of netstate -a | grep 50075 has many
> TIME_WAIT status when this happened.
> partial log in attachment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
