You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2012/08/27 21:22:10 UTC
[jira] [Commented] (FLUME-1426) FileChannel FlumeEventQueue.remove
could be optimized
[ https://issues.apache.org/jira/browse/FLUME-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442641#comment-13442641 ]
Brock Noland commented on FLUME-1426:
-------------------------------------
One option is, during replay, use a CountingBloomFilter (due to addition/deletion facility) to track what is currently on the queue.
http://hadoop.apache.org/common/docs/current/api/org/apache/hadoop/util/bloom/CountingBloomFilter.html
> FileChannel FlumeEventQueue.remove could be optimized
> -----------------------------------------------------
>
> Key: FLUME-1426
> URL: https://issues.apache.org/jira/browse/FLUME-1426
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: v1.2.0
> Reporter: Brock Noland
>
> FlumeEventQueue.remove iterates from the beginning to the end. It's rarely used but when it is used, it's very slow.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira