You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/10/21 15:21:59 UTC

[jira] [Commented] (AMBARI-18660) Log Search schema meta data loader fix

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

Hadoop QA commented on AMBARI-18660:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12834651/AMBARI-18660.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> 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)