You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Otis Gospodnetic (JIRA)" <ji...@apache.org> on 2014/02/28 18:36:39 UTC
[jira] [Commented] (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=13916062#comment-13916062 ]
Otis Gospodnetic commented on FLUME-1045:
-----------------------------------------
Maybe this issue should be Won't Fix or Dupe because FLUME-1227 just got committed?
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)