hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From abhay ratnaparkhi <abhay.ratnapar...@gmail.com>
Subject CLOSE_WAIT connections for jobtracker web interface.
Date Thu, 08 Sep 2011 21:08:38 GMT
Hello,

I am not able to get any response from jobtracker web URL ...
http://severname:50030/jobtracker.jsp
I can see many connections in CLOSE_WAIT state on the server. It seems that
there is some problem in closing a connection by application.
We had asked admin folks to enable monitoring for the jobtracker URL. Is it
possible that it caused a problem? or it's bug in the web application/jetty
server which is not closing connection properly.
Is there any way I can restart jobtracker web application?

Following is the partial o/p of netstat command.


wsiuser@dpev266:~$ netstat | grep '50030'
tcp        0      0 dpev266:50030
monitor102.adtech.int:33651SYN_RECV
tcp        0      0 dpev266:50030
monitor102.adtech.int:34197SYN_RECV
tcp        0      0 dpev266:50030               9.77.202.201:jetform
SYN_RECV
tcp        0      0 dpev266:50030               9.77.202.201:vdmplay
SYN_RECV
tcp        0      0 dpev266:50030
monitor102.adtech.int:34644SYN_RECV
tcp     1127      0 dpev266:50030               ::ffff:9.77.82.162:ff-sm
CLOSE_WAIT
tcp        1      0 dpev266:50030               ::ffff:9.77.82.162:rootd
CLOSE_WAIT
tcp     1160      0 dpev266:50030               ::ffff:9.77.82.162:proofd
CLOSE_WAIT
tcp        1      0 dpev266:50030               ::ffff:9.77.82.162:obrpd
CLOSE_WAIT
tcp        1      0 dpev266:50030               ::ffff:9.77.8:sunclustermgr
CLOSE_WAIT
tcp     1157      0 dpev266:50030               ::ffff:9.77.82.:cnrprotocol
CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:46097CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:44050CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:42258CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:48409CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:58651CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:55326CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:33566CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:52226CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:45834CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:43534CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:60431CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:58928CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:45106CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:58679CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:59449CLOSE_WAIT
tcp      173      0 dpev266:50030
monitor102.adtech.int:47167CLOSE_WAIT

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message