[
https://issues.apache.org/jira/browse/FLUME-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877477#comment-13877477
]
Ashish Paliwal commented on FLUME-2298:
---------------------------------------
2.1 What I meant was, the DC channel code behavior is based on the mode it is
operating in. Rather than having Master DC class and Slave DC class. But may be
I am missing something
2.2 Same as above, when DC channel is running in Slave mode it shall have the
states as mentioned above. This is more at code level than at logical level
3. I am not able to visualize this part. A Source puts a message in DC Channel,
this shall be under transaction, so I assume a transaction would be complete
when Event is put in Master and perhaps Slave(s). This gives implicit ordering.
4. The point I am trying to make is, where would the local Sink send the
Events, if it doesn't have settings. May be I should be more explicit with
Agent hosting Master Channel
5. I am fine with name, was just a thought :)
IMHO, we can get into code as well, making happy scenarios work and move along
with 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,
> 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)
