[
https://issues.apache.org/jira/browse/FLUME-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206657#comment-13206657
]
Juhani Connolly commented on FLUME-865:
---------------------------------------
Ok, here is what I will try to do then:
- Implement the configuration you suggested. This will be backwards compatible
with existing configurations but ignore any properties like
host1.sinks.mysink.runner.* which are already unused.
- Enforce sinks to each be exclusive to a single group. Additionally enforce
all sinks in a group to use the same channel.
- Groups will use the universal sink runner implementation with a pluggable
selector
Does this sound like what you hoped for?
> 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
