[
https://issues.apache.org/jira/browse/AMBARI-17625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368892#comment-15368892
]
Hadoop QA commented on AMBARI-17625:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816925/AMBARI-17625.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 1 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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.security.authorization.AmbariLdapAuthenticationProviderTest
org.apache.ambari.server.security.authorization.AmbariLdapAuthenticationProviderForDuplicateUserTest
org.apache.ambari.server.state.ServicePropertiesTest
org.apache.ambari.server.security.authorization.AmbariLdapAuthenticationProviderForDNWithSpaceTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7753//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7753//console
This message is automatically generated.
> Ambari server log flooded with error messages related to LogSearch service
> --------------------------------------------------------------------------
>
> Key: AMBARI-17625
> URL: https://issues.apache.org/jira/browse/AMBARI-17625
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17625.patch
>
>
> {code:title=ambari-server.log}
> 06 Jul 2016 19:26:28,798 ERROR [ambari-client-thread-2843]
> LoggingSearchPropertyProvider:59 - Error occurred while making request to
> LogSearch service, unable to populate logging properties on this resource
> 06 Jul 2016 19:27:26,865 ERROR [ambari-client-thread-2842]
> LoggingSearchPropertyProvider:59 - Error occurred while making request to
> LogSearch service, unable to populate logging properties on this resource
> 06 Jul 2016 19:28:22,756 ERROR [ambari-client-thread-2699]
> LoggingSearchPropertyProvider:59 - Error occurred while making request to
> LogSearch service, unable to populate logging properties on this resource
> 06 Jul 2016 19:29:10,988 ERROR [ambari-client-thread-2816]
> LoggingSearchPropertyProvider:59 - Error occurred while making request to
> LogSearch service, unable to populate logging properties on this resource
> 06 Jul 2016 19:29:24,700 ERROR [ambari-client-thread-2699]
> LoggingSearchPropertyProvider:59 - Error occurred while making request to
> LogSearch service, unable to populate logging properties on this resource
> {code}
> LogSearch service was not installed on this cluster. But it seems that Ambari
> makes client requests against Logsearch service even when it is not installed
> and keeps logging ERROR messages in ambari-server log
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
