hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhangshilong (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-7608) hdfs dfsclient newConnectedPeer has no read or write timeout
Date Wed, 14 Jan 2015 08:10:36 GMT
zhangshilong created HDFS-7608:

             Summary: hdfs dfsclient  newConnectedPeer has no read or write timeout
                 Key: HDFS-7608
                 URL: https://issues.apache.org/jira/browse/HDFS-7608
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: dfsclient, fuse-dfs
    Affects Versions: 2.6.0, 2.3.0
         Environment: hdfs 2.3.0  hbase 0.98.6
            Reporter: zhangshilong
             Fix For: 2.6.0

hbase compactSplitThread may lock forever on  read datanode blocks.

debug found:  epollwait timeout set to 0,so epollwait can not  run out.

cause: in hdfs 2.3.0
hbase using DFSClient to read and write blocks.
DFSClient  creates one socket using newConnectedPeer(addr), but has no read or write timeout.

in v 2.6.0,  newConnectedPeer has add readTimeout to deal with the problem,but do not add
writeTimeout. why did not adding writeTimeout?

I think NioInetPeer need a default socket timeout,so appalications will no need to force adding
timeout by themselives. 

This message was sent by Atlassian JIRA

View raw message