[
https://issues.apache.org/jira/browse/AMBARI-17277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-17277:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk:
{code:java}
commit 6a6bb7a87f01b125a0cba717f98e2c74af348d06
Author: Miklos Gergely <[email protected]>
Date: Tue Jun 21 16:19:46 2016 +0200
AMBARI-17277. Log Level filter not applied before Log Search Starts at
first (Miklos Gergely via oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit 92c8a265e85ba6783f26f1042dd8d13d7e3e4e15
Author: Miklos Gergely <[email protected]>
Date: Tue Jun 21 16:19:46 2016 +0200
AMBARI-17277. Log Level filter not applied before Log Search Starts at
first (Miklos Gergely via oleewere)
{code}
> 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)
