[
https://issues.apache.org/jira/browse/FLUME-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870381#comment-13870381
]
Ashish Paliwal commented on FLUME-2298:
---------------------------------------
I have done something similar using Hazelcast Distributed Queue and Terracotta
Queue implementations, wrapped under Flume Channel. The only trick would be to
avoid the network hops each time we do put and take Events from the Channel.
These implementations looked Anti-pattern to me for Flume. There could be other
ways of doing a remote persistence.
> 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
>
> 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)
