You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Inder SIngh (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/03/22 12:18:22 UTC

[jira] [Issue Comment Edited] (FLUME-1045) Proposal to support disk based spooling

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

Inder SIngh edited comment on FLUME-1045 at 3/22/12 11:17 AM:
--------------------------------------------------------------

Initial version of patch contains following

1. Skeleton code to disk based solution proposed in this JIRA.

Disclamer - This patch isn't functional/complete yet.
Objective is to get community consensus around the proposal.



                
      was (Author: inder):
    Initial version of patch contains following

1. Skeleton code to disk based solution proposed in this patch.


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