[ 
https://issues.apache.org/jira/browse/YARN-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850539#comment-13850539
 ] 

Hudson commented on YARN-1145:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1641 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1641/])
YARN-1145. Fixed a potential file-handle leak in the web interface for 
displaying aggregated logs. Contributed by Rohith Sharma. (vinodkv: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1551326)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/AggregatedLogFormat.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/webapp/log/AggregatedLogsBlock.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/logaggregation/TestAggregatedLogFormat.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/logaggregation/TestAggregatedLogsBlock.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/logaggregation/AppLogAggregatorImpl.java


> Potential file handle leak in aggregated logs web ui
> ----------------------------------------------------
>
>                 Key: YARN-1145
>                 URL: https://issues.apache.org/jira/browse/YARN-1145
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.0.5-alpha, 0.23.9, 2.1.1-beta
>            Reporter: Rohith
>            Assignee: Rohith
>             Fix For: 2.4.0
>
>         Attachments: MAPREDUCE-5486.patch, YARN-1145.1.patch, 
> YARN-1145.2.patch, YARN-1145.3.patch, YARN-1145.4.patch, YARN-1145.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to