[
https://issues.apache.org/jira/browse/FLUME-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604035#comment-13604035
]
Brock Noland commented on FLUME-1917:
-------------------------------------
I think this is going to require refactoring of code and also our approach to
how to we commit. From my perspective, what we want to avoid is:
thread-1: write event1
thread-2: write event2
thread-1: write event3
thread-2: commit and sync
thread-1: commit and sync (immediately after thread-2)
That is we don't want multiple threads doing subsequent commits and then syncs.
It'd be ideal if we had:
thread-1: write event1
thread-2: write event2
thread-1: write event3
thread-2: commit
thread-1: commit
thread-2: sync
thread-1: sync -- noop sync we already synced our commit.
> FileChannel group commit (coalesce fsync)
> -----------------------------------------
>
> Key: FLUME-1917
> URL: https://issues.apache.org/jira/browse/FLUME-1917
> Project: Flume
> Issue Type: Bug
> Components: File Channel
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
>
--
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
