[
https://issues.apache.org/jira/browse/FLUME-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877484#comment-13877484
]
Ted Malaska commented on FLUME-2298:
------------------------------------
2.1 and 2.2 I think this is where we differ. DC doesn't run in master or slave
mode. It always contains a master and 1 or more slaves.
3. Yes and now. I believed that too at first and then Hari opened my eyes to
asych puts and not knowing which command would finish first. The case where
the event A when in to the master before event B and B went into the slave
before A is very possible if ordering is not in forced or if the whole process
is not in closed in a sych block.
4. Ever Agent will have source and sink connected to a DC. This kind goes with
2.1 and 2.2. A DC is both master and slave(s) not ether.
> 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,
> FlumeDistributedChannelDesign.0.2.1.pdf, FlumeDistributedChannelDesign.0.2.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)
