[ 
https://issues.apache.org/jira/browse/FLUME-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206637#comment-13206637
 ] 

Juhani Connolly commented on FLUME-865:
---------------------------------------

I guess that backwards compatibility is a target then? I had that in mind when 
I made the current configuration(which is slightly unwieldy)

Your suggested configuration is shorter than the current one I have implemented 
and possibly easier to understand. One potential source of confusion that is in 
it  is whether sinks must be exclusive to one group. I guess each group would 
basically translate to a separate runner... If we went with this configuration, 
perhaps we should be removing the concept of runners attached to individual 
sinks entirely? At the moment the configuration has them as subcomponents of 
each sink(which is why I did the configuration the way it is in this patch)

Personally I would like to ship this patch as is(the current configuration is 
fully backwards compatible), and make the sink selector/configuration a 
separate issue(I already started a separate discussion thread for it in 
FLUME-952 where Jarcec has made another good suggestion for configuration, but 
one that is incompatible with existing configs)
                
> 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

        

Reply via email to