[
https://issues.apache.org/jira/browse/FLUME-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210013#comment-13210013
]
Juhani Connolly commented on FLUME-865:
---------------------------------------
Working on the configuration now, could use some input:
What shall we do when a sink group is invalidated because one of its sinks is
missing? I see us as having 2 options, neither that I particularly like:
- Ignore the missing sink, only marking the group as invalid if it has no sinks
- Invalidate the set if any sinks are missing. The problem with this is that
"unattached" sinks would then run independenly of a group, thus competing with
one another for channel resources, when in normal functioning a group and its
designated processor should be assigning work to each sink
> 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
