ambari-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] (AMBARI-22172) Change log level for ClusterNotFoundException
Date Tue, 10 Oct 2017 13:39:00 GMT

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

Hadoop QA commented on AMBARI-22172:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12891246/AMBARI-22172.patch
  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
tests.
                        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 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12471//console

This message is automatically generated.

> Change log level for ClusterNotFoundException
> ---------------------------------------------
>
>                 Key: AMBARI-22172
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22172
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-22172.patch
>
>
> ClusterNotFoundExceptions are filling log files unecesarly, when somebody is polling
Ambari with a non existing clusterId. Logging a warning on INFO level (eventually log stacktrace
on DEBUG level) should be enough.
> {code}
> 19 Apr 2017 06:25:27,570 ERROR [ambari-client-thread-29] AmbariManagementControllerImpl:1128
- Cluster not found
> org.apache.ambari.server.ClusterNotFoundException: Cluster not found, clusterName=kudeep100node
>         at org.apache.ambari.server.state.cluster.ClustersImpl.getCluster(ClustersImpl.java:277)
>         at org.apache.ambari.server.controller.AmbariManagementControllerImpl.getHostComponents(AmbariManagementControllerImpl.java:1126)
>         at org.apache.ambari.server.controller.AmbariManagementControllerImpl.getHostComponents(AmbariManagementControllerImpl.java:3451)
>         at org.apache.ambari.server.controller.internal.HostComponentResourceProvider$2.invoke(HostComponentResourceProvider.java:216)
>         at org.apache.ambari.server.controller.internal.HostComponentResourceProvider$2.invoke(HostComponentResourceProvider.java:213)
>         at org.apache.ambari.server.controller.internal.AbstractResourceProvider.getResources(AbstractResourceProvider.java:307)
>         at org.apache.ambari.server.controller.internal.HostComponentResourceProvider.findResources(HostComponentResourceProvider.java:213)
>         at org.apache.ambari.server.controller.internal.HostComponentResourceProvider.getResources(HostComponentResourceProvider.java:189)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message