[
https://issues.apache.org/jira/browse/FLUME-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206651#comment-13206651
]
Arvind Prabhakar commented on FLUME-865:
----------------------------------------
Good points Juhani.
* Regarding the exclusivity of sinks - that needs to be handled via the
FlumeConfiguration.validateConfiugration() method. There are other rules to
honor too - one that comes to mind is that all sinks in a group must be
associated with the same channel. Such rules are way too complex to be able to
express in properties file syntax - and therefore require the
parsing/validation to be provided separately.
* The notion of pluggable runners is no longer applicable since there is only a
single sink type. What we have now is a single concrete sink runner
implementation that will be responsible for the entire sink processing
functionality. Consequently, any extension we do must take into account that
the concerete sink runner is here to stay and works with it.
I think the current patch is eighty percent there already and with your help we
can get it committed fast. If we push the patch in its current state, we are
likely creating more configuration dialects that we will be bound to support
going forward. Hence it is best to address the configuration part before
pushing this in.
If you would like to seek help in factoring out parts of this work to others,
please feel free to create sub-tasks/other JIRAs that identify the details and
one of us can jump in to help.
> 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
