[
https://issues.apache.org/jira/browse/FLUME-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180547#comment-13180547
]
Peter Newcomb commented on FLUME-896:
-------------------------------------
I've filled in the existing FileChannel skeleton, but have simplified it in
that I'm persisting each event as its own file in order to avoid problems with
asynchronous source and sink transaction boundaries. There are 4
subdirectories that each file transitions among: writing, complete, reading,
and removed. Within each subdirectory, event files are contained within
transaction subdirectories, so that whole transactions can be moved from one
state to another atomically (at least to the limits of the underlying
filesystem).
Though I have this code up and running and on its way towards production, I
have not yet completed performance and load testing nor test cases, and hence
have not posted the patch for review, though I hope to do so soon.
> Implement file write ahead log channel
> --------------------------------------
>
> Key: FLUME-896
> URL: https://issues.apache.org/jira/browse/FLUME-896
> Project: Flume
> Issue Type: New Feature
> Components: Channel
> Affects Versions: NG alpha 1
> Reporter: E. Sammer
> Assignee: Peter Newcomb
> Fix For: v1.1.0
>
>
> Implement a channel that uses a regular file system and a write ahead log for
> durable event delivery.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
