You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/02/18 20:33:18 UTC

[jira] [Commented] (AMBARI-15091) Metrics collector running out of file descriptors

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

Hadoop QA commented on AMBARI-15091:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12788469/AMBARI-15091-trunk.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 7 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 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 ambari-metrics/ambari-metrics-common ambari-metrics/ambari-metrics-timelineservice ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/5450//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5450//console

This message is automatically generated.

> Metrics collector running out of file descriptors
> -------------------------------------------------
>
>                 Key: AMBARI-15091
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15091
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.2.2
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15091-trunk.patch
>
>
> 1200 node cluster:
> {code}
> [root@perf-a-2 ~]# lsof -p 4100 | wc -l
> 32928
> {code}
> Exception in collector logs:
> {code}
> 2016-02-05 15:51:50,528 WARN org.mortbay.log: EXCEPTION
> java.io.IOException: Too many open files
>         at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
>         at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422)
>         at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250)
>         at org.mortbay.jetty.nio.SelectChannelConnector$1.acceptChannel(SelectChannelConnector.java:75)
>         at org.mortbay.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:695)
>         at org.mortbay.io.nio.SelectorManager.doSelect(SelectorManager.java:193)
>         at org.mortbay.jetty.nio.SelectChannelConnector.accept(SelectChannelConnector.java:124)
>         at org.mortbay.jetty.AbstractConnector$Acceptor.run(AbstractConnector.java:708)
>         at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> {code}
> The client side connections are also open and there are plenty of CLOSE_WAIT sockets.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)