You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Olivér Szabó (JIRA)" <ji...@apache.org> on 2016/05/08 10:58:12 UTC

[jira] [Commented] (AMBARI-16283) In LogSearch, the order of component start is incorrect

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

Olivér Szabó commented on AMBARI-16283:
---------------------------------------

it looks exactly like you described
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.3/services/LOGSEARCH/role_command_order.json

Although, with blueprints, components only wait eash other in the same host.

> In LogSearch, the order of component start is incorrect
> -------------------------------------------------------
>
>                 Key: AMBARI-16283
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16283
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-logsearch
>            Reporter: Don Bosco Durai
>            Assignee: Olivér Szabó
>
> The correct to start components in LogSearch is:
> Solr
> Log Search app - This creates the collections if required
> Log Feeder 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)