-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.3.0, 2.6.0
-
Fix Version/s: 2.8.0, 3.0.0-alpha1
-
Component/s: fuse-dfs, hdfs-client
-
Labels:None
-
Environment:
hdfs 2.3.0 hbase 0.98.6
-
Target Version/s:
problem:
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 added readTimeout to deal with the problem,but did not add writeTimeout. why did not add write Timeout?
I think NioInetPeer need a default socket timeout,so appalications will no need to force adding timeout by themselives.
- breaks
-
HDFS-8785 TestDistributedFileSystem is failing in trunk
-
- Resolved
-
-
HDFS-8812 TestDistributedFileSystem#testDFSClientPeerWriteTimeout fails
-
- Resolved
-
- is related to
-
HDFS-8359 Normalization of timeouts in InputStream and OutputStream
-
- Open
-
- relates to
-
HDFS-7005 DFS input streams do not timeout
-
- Closed
-