[
https://issues.apache.org/jira/browse/FLUME-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188353#comment-13188353
]
Juhani Connolly commented on FLUME-865:
---------------------------------------
I'm also interested in this... and the configuration that Jarek is thinking of
sounds fine.
The thing that I'm getting stuck on considering how an implementation would
work is the fact that sinks are configured against a channel which they
actively consume from, as opposed to being pushed to.
Having a failover sink with subsinks would mean the subsink would have to know
about the parent.
With that in mind, rather than a sink, implement this type of failover as a
channel that consumes from another channel when take() is called upon it.
- Track the active sink, refusing take requests from other sinks
- If the active sink stops taking from the channel, failover to the next sink,
making that the active one.
- Should a higher priority sink make a request, restore that to the active sink
What do you think?
> 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
>
> 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
