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

Hudson commented on AMBARI-17307:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #5115 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5115/])
AMBARI-17307. LogFeeder output to Solr doesn't handle empty buffer queue 
(oleewere: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9825bc2140948ace88fa06a1b03bbab9f20f2a4d])
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputSolr.java


> 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
>          Components: ambari-logsearch
>    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)

Reply via email to