[
https://issues.apache.org/jira/browse/FLUME-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230362#comment-13230362
]
Hari Shreedharan commented on FLUME-962:
----------------------------------------
Thanks Arvind, that clears up some doubts. But do we really want to take a
properties or configuration file? This will be provided as an API right? So I
think we should just take a map or list of end points, rather than having to
force a configuration file on the client. My idea was to provide the basic
connect/send/disconnect API, and keep track of the end points internally, for
this I don't see why a conf or properties would be required. Maybe the client
code generates this list on the fly(say they are running on EC2 or some shared
cluster?), in which case a config file or properties object gives us no real
advantage.
> Failover capability for Client SDK
> ----------------------------------
>
> Key: FLUME-962
> URL: https://issues.apache.org/jira/browse/FLUME-962
> Project: Flume
> Issue Type: Sub-task
> Affects Versions: v1.0.0
> Reporter: Kathleen Ting
> Fix For: v1.2.0
>
>
> Need a client SDK for Flume that will allow clients to be able to failover
> from one source to another in case the first agent is not available. This
> will help in keeping client implementations developed outside of the project
> decoupled from internal details of HA implementation within Flume.
--
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
