You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/06/13 17:16:21 UTC
[jira] [Commented] (AMBARI-17136) If Solr is down or not ready,
then LogFeeder to should retry
[ https://issues.apache.org/jira/browse/AMBARI-17136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327773#comment-15327773 ]
Hudson commented on AMBARI-17136:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #5066 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5066/])
AMBARI-17136. If Solr is down or not ready, then LogFeeder to should (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0821a3111e1e6e524328bb8a9e1c452f6127f00f])
* ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputSolr.java
> 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)