ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivér Szabó (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-17136) If Solr is down or not ready, then LogFeeder to should retry
Date Mon, 13 Jun 2016 14:36:21 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-17136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Olivér Szabó resolved AMBARI-17136.
-----------------------------------
    Resolution: Fixed

committed to trunk:
{code:java}
commit 0821a3111e1e6e524328bb8a9e1c452f6127f00f
Author: oleewere <oleewere@gmail.com>
Date:   Mon Jun 13 13:23:25 2016 +0200

    AMBARI-17136. If Solr is down or not ready, then LogFeeder to should retry (Bosco Durai
via oleewere)
{code}

committed to branch-2.4
{code:java}
commit 151c0fd578ec3217293aceafa1f33b55b536a7ad
Author: oleewere <oleewere@gmail.com>
Date:   Mon Jun 13 13:23:25 2016 +0200

    AMBARI-17136. If Solr is down or not ready, then LogFeeder to should retry (Bosco Durai
via oleewere)
{code}

> If Solr is down or not ready, then LogFeeder to should retry 
> -------------------------------------------------------------
>
>                 Key: AMBARI-17136
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17136
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-logsearch
>            Reporter: Don Bosco Durai
>            Assignee: Don Bosco Durai
>             Fix For: 2.4.0
>
>
> Currently, only for IOException LogFeeder does retry. We should do it for all SolrException



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

Mime
View raw message