[ 
https://issues.apache.org/jira/browse/HDFS-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886083#action_12886083
 ] 

Cody Saunders commented on HDFS-693:
------------------------------------

I have also seen this, and believe it may go back to Java + Timezone issues. I 
found a possibly related thread:

http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-user/201004.mbox/%3c670102.35052...@web52303.mail.re2.yahoo.com%3e

With summary:

" s...@ubuntu-namenode:~/testtime$ java testDateTime 
date: Thu Apr 22 11:37:32 PST 2010
s...@ubuntu-namenode:~/testtime$ date
Thu Apr 22 12:37:34 PDT 2010
s...@ubuntu-namenode:~/testtime$ cat /etc/timezone 
America/Los_Angeles

but then says:

s...@ubuntu-hadoop-1:~/testtime$ java testDateTime
date: Thu Apr 22 12:38:11 PDT 2010
s...@ubuntu-hadoop-1:~/testtime$ date
Thu Apr 22 12:38:12 PDT 2010
s...@ubuntu-hadoop-1:~/testtime$ cat /etc/timezone 
America/Los_Angeles"


....It looks like this person is saying that testDateTime sometimes works 
exactly right and other times does not... We can probably get around it by 
using "TZ" in the environment for Java, which is what I'm trying currently. So 
far, haven't seen more 480s timeouts.

> 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.

Reply via email to