[
https://issues.apache.org/jira/browse/AMBARI-18660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-18660:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk:
{code:java}
commit 3bb4ec107054aefecc7471d87521bb8efdd923a7
Author: Miklos Gergely <[email protected]>
Date: Sat Nov 5 14:42:36 2016 +0100
AMBARI-18660. Log Search schema meta data loader fix (Miklos Gergely via
oleewere)
Change-Id: Ibbf3f15984b3439e25cb2b7f06be1830aa389240
{code}
comitted to branch-2.5:
{code:java}
commit 59c839c87352d88998d0f8febb92eedfb18f0385
Author: Miklos Gergely <[email protected]>
Date: Sat Nov 5 14:42:36 2016 +0100
AMBARI-18660. Log Search schema meta data loader fix (Miklos Gergely via
oleewere)
Change-Id: Ibbf3f15984b3439e25cb2b7f06be1830aa389240
{code}
> Log Search schema meta data loader fix
> --------------------------------------
>
> Key: AMBARI-18660
> URL: https://issues.apache.org/jira/browse/AMBARI-18660
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.4.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-18660.patch
>
>
> Log Search periodically queries the solr for the field meta data, which may
> not work on some clusters. Scheduling this task should be done by spring.
> Also the luke request sent for this purpose must be requested from each
> shard, and the results must be summarized. Unfortunately the solr client can
> not be used for this purpose because it sends it to random shard.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
