Details
Description
HBase dose not close a dead connection with the datanode.
This resulting in over 60K CLOSE_WAIT and at some point HBase can not connect to the datanode because too many mapped sockets from one host to another on the same port.
The example below is with low CLOSE_WAIT count because we had to restart hbase to solve the porblem, later in time it will incease to 60-100K sockets on CLOSE_WAIT
[root@hd2-region3 ~]# netstat -nap |grep CLOSE_WAIT |grep 21592 |wc -l
13156
[root@hd2-region3 ~]# ps -ef |grep 21592
root 17255 17219 0 12:26 pts/0 00:00:00 grep 21592
hbase 21592 1 17 Aug29 ? 03:29:06 /usr/java/jdk1.6.0_26/bin/java -XX:OnOutOfMemoryError=kill -9 %p -Xmx8000m -ea -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -Dhbase.log.dir=/var/log/hbase -Dhbase.log.file=hbase-hbase-regionserver-hd2-region3.swnet.corp.log ...
Attachments
Attachments
Issue Links
- is related to
-
HADOOP-14747 S3AInputStream to implement CanUnbuffer
- Resolved
-
HADOOP-14748 Wasb input streams to implement CanUnbuffer
- Resolved
-
HBASE-18212 In Standalone mode with local filesystem HBase logs Warning message:Failed to invoke 'unbuffer' method in class class org.apache.hadoop.fs.FSDataInputStream
- Resolved
- relates to
-
HADOOP-14765 AdlFsInputStream should implement unbuffer
- Resolved
-
HADOOP-12724 Let BufferedFSInputStream implement CanUnbuffer
- Open
-
HADOOP-12805 Annotate CanUnbuffer with @InterfaceAudience.Public
- Closed
-
HBASE-24155 When running the tests, a tremendous number of connections are put into TIME_WAIT.
- Resolved