[
https://issues.apache.org/jira/browse/AMBARI-17277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334058#comment-15334058
]
Hadoop QA commented on AMBARI-17277:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811102/AMBARI-17277.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-logfeeder ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7374//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7374//console
This message is automatically generated.
> Log Level filter not applied before Log Search Starts at first
> --------------------------------------------------------------
>
> Key: AMBARI-17277
> URL: https://issues.apache.org/jira/browse/AMBARI-17277
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.4.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17277.patch
>
>
> After Log Search is started it sends the filters to the Solr which describes
> what log levels should be persisted. In the meantime Logfeeders start to push
> their data, which is not filtered. The result is misleading, the user may
> find it add that some specific level logs are loaded, others are not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
