You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2013/08/29 08:03:51 UTC

[jira] [Created] (MAPREDUCE-5486) Potential file handler leak in JobHistoryServer web ui.

Rohith Sharma K S created MAPREDUCE-5486:
--------------------------------------------

             Summary: Potential file handler leak in JobHistoryServer web ui.
                 Key: MAPREDUCE-5486
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5486
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: jobhistoryserver
    Affects Versions: 2.0.5-alpha, 2.1.1-beta
            Reporter: Rohith Sharma K S


Any problem in getting aggregated logs for rendering on web ui, then LogReader is not closed. 

Now, it reader is not closed which causing many connections in close_wait state.

hadoopuser@hadoopuser:> jps
*27909* JobHistoryServer

DataNode port is 50010. When greped with DataNode port, many connections are in CLOSE_WAIT from JHS.
hadoopuser@hadoopuser:> netstat -tanlp |grep 50010
tcp        0      0 10.18.40.48:50010       0.0.0.0:*               LISTEN      21453/java          
tcp        1      0 10.18.40.48:20596       10.18.40.48:50010       CLOSE_WAIT  *27909*/java          
tcp        1      0 10.18.40.48:19667       10.18.40.152:50010      CLOSE_WAIT  *27909*/java          
tcp        1      0 10.18.40.48:20593       10.18.40.48:50010       CLOSE_WAIT  *27909*/java          
tcp        1      0 10.18.40.48:12290       10.18.40.48:50010       CLOSE_WAIT  *27909*/java          
tcp        1      0 10.18.40.48:19662       10.18.40.152:50010      CLOSE_WAIT  *27909*/java          

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira