[
https://issues.apache.org/jira/browse/FLUME-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Malaska updated FLUME-2298:
-------------------------------
Attachment: Flume Replication Channel Design.0.3.pdf
Had a great meeting with the Flume Team yesterday and I've made updates to the
doc:
1. Changed name to Replication Channel ( Ashish Paliwal you were right on this.
Thx)
2. Updated the Goals
3. Added Non-Goals
4. Added diagrams and text to explain the design is simpler then the
distributed channel name suggest
5. Added the consensus method of 2PC with timeout
Thank you Flume Committers
> Replication 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: Flume Replication Channel Design.0.3.pdf,
> 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)
