[
https://issues.apache.org/jira/browse/FLUME-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206663#comment-13206663
]
Arvind Prabhakar commented on FLUME-865:
----------------------------------------
Thanks Juhani - this sounds good to me. One clarification though:
There should not be a concept of a pluggable selector since from the sink
runner perspective there is no selection to be made. For example - if the
selector were to identify a sink and the runner finds that the selected sink's
process method has failed - then the notion of failover policy will leak into
the runner implementation. Therefore, a targeted abstraction would be a
pluggable sink processor that works on the group of sinks and exposes a single
process method. The implementation of the process method would embody the
policy that the processor provides.
Does that sound reasonable to you?
> Implement failover sink
> ------------------------
>
> Key: FLUME-865
> URL: https://issues.apache.org/jira/browse/FLUME-865
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Affects Versions: NG alpha 2
> Reporter: Jarek Jarcec Cecho
> Assignee: Juhani Connolly
> Fix For: v1.1.0
>
> Attachments: FLUME-865.patch
>
>
> It would be nice if the flume-ng would have ability to failover to different
> sink in case that the active one is not responding (e.g. before failing the
> transaction).
--
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
