[
https://issues.apache.org/jira/browse/YARN-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814847#comment-13814847
]
Hadoop QA commented on YARN-1145:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12612346/YARN-1145.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2383//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2383//console
This message is automatically generated.
> 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 Sharma K S
> Assignee: Rohith Sharma K S
> 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#6144)
