You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2014/04/28 17:28:17 UTC
[jira] [Commented] (FLUME-2298) Replication Channel
[ https://issues.apache.org/jira/browse/FLUME-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983100#comment-13983100 ]
Ashish Paliwal commented on FLUME-2298:
---------------------------------------
I finally got some time to whip out a very crude implementation using Hazelcast. The implementation is essentially a copy of Memory Channel, replacing the Deque with Hazelcast distributed queue. Have been able to make one simple putTake test case pass.
It still needs a little more work to make the crude scattered code into simpler flow. Hopefully, shall be able to push the changes by weekend.
> 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.2#6252)