File Channel is designed based on the Log Structured File System. Every time a source writes the event the event is written to disk too, and is really available to the sinks only when that transaction is committed.
On this sink side, every take is written to the disk (each take simply has the file id and offset of the original event), but the events are garbage collected if and only the transaction is committed. Also, only commits we actually fsync to disk. You can see more details of the design here: https://blogs.apache.org/flume/entry/apache_flume_filechannel Hari On Wed, Feb 26, 2014 at 10:18 AM, Otis Gospodnetic < [email protected]> wrote: > Hi, > > Does Flume's File Channel write to disk right away? Or only after it > attempts to send data to the Source? (e.g. if sending fails) > > I think it's the former because Channel knows nothing about Source/sending > AFAIK, but am hoping for the latter. :) > > Thanks, > Otis > -- > Performance Monitoring * Log Analytics * Search Analytics > Solr & Elasticsearch Support * http://sematext.com/ > >
