hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1145) Potential file handle leak in aggregated logs web ui
Date Fri, 06 Sep 2013 03:47:52 GMT

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

Hadoop QA commented on YARN-1145:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/1853//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1853//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,
> Any problem in getting aggregated logs for rendering on web ui, then LogReader is not
> 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*               LISTEN      21453/java
> tcp        1      0       CLOSE_WAIT  *27909*/java
> tcp        1      0      CLOSE_WAIT  *27909*/java
> tcp        1      0       CLOSE_WAIT  *27909*/java
> tcp        1      0       CLOSE_WAIT  *27909*/java
> tcp        1      0      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

View raw message