You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ferenc Szabo (JIRA)" <ji...@apache.org> on 2017/09/01 16:38:02 UTC
[jira] [Commented] (FLUME-3149) reduce cpu cost for file source
transfer while still maintaining reliability
[ https://issues.apache.org/jira/browse/FLUME-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150803#comment-16150803 ]
Ferenc Szabo commented on FLUME-3149:
-------------------------------------
Hi [~zyfo2], [~bessbd]
as a brainstorming starter idea: we could have a PollableSourceChannel implementation where the channel would behave as a wrapper around a PollableSource (TailDirSource is one of them) and while the Pollable source can keep track of where it is in the processing, the channel can work without copying the data into a buffer and keeping track of its buffer. That would definitely use less resources.
Let me know what you think about the idea.
I'm happy to help with the implementation and the testing if needed.
Thank you,
Ferenc
> reduce cpu cost for file source transfer while still maintaining reliability
> ----------------------------------------------------------------------------
>
> Key: FLUME-3149
> URL: https://issues.apache.org/jira/browse/FLUME-3149
> Project: Flume
> Issue Type: Improvement
> Components: File Channel
> Reporter: will zhang
>
> File channel tracks transferred events and use transnational mechanism to make transfer recoverable. However, it increases CPU cost due to frequent system calls like write, read, etc. The Cpu cost could be very high if the transfer rate is high. In contrast, Memory channel has no such issue which requires only about 10% of CPU cost in the same environment but it's not recovered if the system is down accidentally.
> For sources like taildir/spooldir, I propose we could track offsets of file and store them locally to achieve reliability while still using memory channel to reduce CPU cost. Actually, I have already implemented this feature by storing the offsets in event headers and passing it to my own "offsetMemoryChannel" and store theses offsets in local disk in our production which reduces CPU cost by about 90 percent.
> Please let me know if it's worthwhile to have this feature in community version. Thank you.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)