[ 
https://issues.apache.org/jira/browse/FLUME-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285439#comment-13285439
 ] 

Sharad Agarwal commented on FLUME-1045:
---------------------------------------

What I understand from FLUME-1201 is that it proposes primary and secondary 
channels as the first class higher level concept in FLUME, where a new channel 
can be created by composing any arbitrary channels in a hierarchy.
However here the difference is that we are creating a very *specific* channel 
type whose contract and transaction semantics are clearly well defined. Instead 
of rewriting the full implementation from scratch, it just leverages the 
existing implementations. Also note that it only depends on the public and 
defined contract of the specific channels and not depending on their internal 
implementations. This should be ok IMO.

                
> Proposal to support disk based spooling
> ---------------------------------------
>
>                 Key: FLUME-1045
>                 URL: https://issues.apache.org/jira/browse/FLUME-1045
>             Project: Flume
>          Issue Type: New Feature
>    Affects Versions: v1.0.0
>            Reporter: Inder SIngh
>            Priority: Minor
>              Labels: patch
>         Attachments: FLUME-1045-1.patch, FLUME-1045-2.patch
>
>
> 1. Problem Description 
> A sink being unavailable at any stage in the pipeline causes it to back-off 
> and retry after a while. Channel's associated with such sinks start buffering 
> data with the caveat that if you are using a memory channel it can result in 
> a domino effect on the entire pipeline. There could be legitimate down times 
> eg: HDFS sink being down for name node maintenance, hadoop upgrades. 
> 2. Why not use a durable channel (JDBC, FileChannel)?
> Want high throughput and support sink down times as a first class use-case.

--
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

        

Reply via email to