You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2015/07/08 02:03:04 UTC

[jira] [Commented] (FLUME-2632) High CPU on KafkaSink

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

Ashish Paliwal commented on FLUME-2632:
---------------------------------------

[~gwenshap] Can you have a look at it, minor fix.

> High CPU on KafkaSink
> ---------------------
>
>                 Key: FLUME-2632
>                 URL: https://issues.apache.org/jira/browse/FLUME-2632
>             Project: Flume
>          Issue Type: Bug
>          Components: Sinks+Sources
>    Affects Versions: v1.5.1
>            Reporter: Gwen Shapira
>            Assignee: Gwen Shapira
>              Labels: kafka
>             Fix For: 1.6
>
>         Attachments: FLUME-2632-0.patch
>
>
> Reported here: https://github.com/harishreedharan/flume/issues/1
> "I tried flume-ng-kafka-sink and it worked fine. But I noticed that the cpu utilization stay at 100% and never dropped down all the time even at the time the channel is empty.
> I looked into the source code and found that "process" function in KafkaSink always return Status.READY even if no events available in channel. That causes the SinkRunner keep running achieving event from channel and get nothing.
> Do we need to change to return Status.BACKOFF in "process" function in KafkaSink when it notices that there is no events processed in current round? So that the SinkRunner has a chance to take a rest when there is no event in channel. If this proposal feasible, function "testEmptyChannel" in TestKafkaSink also need to be changed. "



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