[
https://issues.apache.org/jira/browse/FLUME-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872212#comment-13872212
]
Ashish Paliwal commented on FLUME-2298:
---------------------------------------
[~ted.m] This is good start. Had a quick glance at the design, some quick
questions/comments
With Master and Slave *channel*, we are referring to the persistence of Channel
data then Channel itself or it's a Channel instance on a different node
With 1:N Master-Slave configuration we run into the issues of Distributed
transactions. Does the implementation consider tunable Consistency or it shall
update all slaves/replicas keeping a consistent view. Looks very much like the
way SolrCloud works
How would the Master-Slave selection process work? Curator has a recipe for it,
but it would need to part of DC impl
I shall look into the paper again tomorrow. Thanks for sharing the design.
> Distributed Channel
> -------------------
>
> Key: FLUME-2298
> URL: https://issues.apache.org/jira/browse/FLUME-2298
> Project: Flume
> Issue Type: New Feature
> Components: Channel
> Reporter: Ted Malaska
> Assignee: Ted Malaska
> Attachments: FlumeDistributedChannelDesign.0.1.pdf
>
>
> This channel will allow for events to be persisted with a plugable method on
> more then one agent or node.
> The goal is to gain the following benefits:
> 1. Events will continue to flow to sinks with out loss or with out large
> delay even in the case of node failure.
> 2. Protect against loss in the case of a complete single node failure
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
