[
https://issues.apache.org/jira/browse/AMBARI-17601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-17601.
-----------------------------------
Resolution: Fixed
committed to trunk:
{code:java}
commit 4eb2be46e21c9a4dd94785985acb8a9818ef246d
Author: oleewere <oleew...@gmail.com>
Date: Thu Jul 7 17:38:28 2016 +0200
AMBARI-17601. Add retry logic for Log Search service check (oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit d6bcffd25230c84799cf86ed5dd8b8044fd64436
Author: oleewere <oleew...@gmail.com>
Date: Thu Jul 7 17:38:28 2016 +0200
AMBARI-17601. Add retry logic for Log Search service check (oleewere)
{code}
> Add retries for LogSearch service check
> ---------------------------------------
>
> Key: AMBARI-17601
> URL: https://issues.apache.org/jira/browse/AMBARI-17601
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, ambari-server
> Affects Versions: 2.4.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Fix For: 2.4.0
>
>
> In some cases, if there are not that many services on the cluster, or just
> adding only the logsearch service, logsearch has not started as quickly as
> service check called
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
