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/06/20 16:19:05 UTC
[jira] [Commented] (AMBARI-17307) LogFeeder output to Solr doesn't
handle empty buffer queue properly
[ https://issues.apache.org/jira/browse/AMBARI-17307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339826#comment-15339826 ]
Olivér Szabó commented on AMBARI-17307:
---------------------------------------
committed to trunk:
{code:java}
commit 9825bc2140948ace88fa06a1b03bbab9f20f2a4d
Author: oleewere <ol...@gmail.com>
Date: Mon Jun 20 18:14:09 2016 +0200
AMBARI-17307. LogFeeder output to Solr doesn't handle empty buffer queue properly (Bosco Durai via oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit 6b33a6c27d4e835d586a05cd22e34701f9e41a3b
Author: oleewere <ol...@gmail.com>
Date: Mon Jun 20 18:14:09 2016 +0200
AMBARI-17307. LogFeeder output to Solr doesn't handle empty buffer queue properly (Bosco Durai via oleewere)
{code}
> LogFeeder output to Solr doesn't handle empty buffer queue properly
> -------------------------------------------------------------------
>
> Key: AMBARI-17307
> URL: https://issues.apache.org/jira/browse/AMBARI-17307
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Don Bosco Durai
> Assignee: Don Bosco Durai
> Fix For: 2.4.0
>
>
> Currently, if the log buffer is empty, then LogFeeder will loop without pausing to check the queue. This spikes the CPU to 100% due to the tight loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)