[
https://issues.apache.org/jira/browse/HDFS-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886166#action_12886166
]
Cody Saunders commented on HDFS-693:
------------------------------------
Last thing to say, setting the dfs.socket.write.timeout to 0 is so far the best
workaround I've discovered. I may try other values to see if I can find the
upper limit, but if it is near an hour, starts to seem like timezone jumps. I'm
using java 1.6.0_16. Could it be the hadoop call or the java call is relying on
uninit var to decide if daylight savings hour...?
> 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.
