2011/5/15 Gaojinchao <[email protected]>: > I try to reproduce the issue that socket is close_wait and find a new issue > thread leak for hmaster process. >
We are leaking threads? What thread (Can you diff thread dumps and see what the name of the new thread is? That would be a clue). > In this case, It seems LogSyncer thread can't be closed > Hlog can't be closed when use api createHRegion. > Why not? It looks like its a daemon thread. Is it stuck in a wait? > It also find some CLOSE_WAIT. But I am not sure what' up. > I need keep digging. > > tcp 227 0 157.5.100.1:60000 157.5.100.1:52780 CLOSE_WAIT > tcp 1 0 157.5.100.1:60000 157.5.100.5:56633 CLOSE_WAIT > tcp 233 0 157.5.100.1:60000 157.5.100.4:50772 CLOSE_WAIT > tcp 227 0 157.5.100.1:60000 157.5.100.1:59921 CLOSE_WAIT > tcp 233 0 157.5.100.1:60000 157.5.100.3:37877 CLOSE_WAIT > tcp 233 0 157.5.100.1:60000 157.5.100.5:57556 CLOSE_WAIT > tcp 233 0 157.5.100.1:60000 157.5.100.5:44967 CLOSE_WAIT > tcp 233 0 157.5.100.1:60000 157.5.100.3:45944 CLOSE_WAIT > C4C1:/opt/hbasetools # netstat -an |grep 60000 | grep CLOSE_WAIT | wc -l > 140 > Do please keep digging. St.Ack
