You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Lior Zeno (JIRA)" <ji...@apache.org> on 2016/07/23 09:02:20 UTC

[jira] [Updated] (FLUME-2173) Exactly once semantics for Flume

     [ https://issues.apache.org/jira/browse/FLUME-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lior Zeno updated FLUME-2173:
-----------------------------
    Fix Version/s: v2.0.0

> Exactly once semantics for Flume
> --------------------------------
>
>                 Key: FLUME-2173
>                 URL: https://issues.apache.org/jira/browse/FLUME-2173
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Hari Shreedharan
>            Assignee: Hari Shreedharan
>             Fix For: v2.0.0
>
>
> Currently Flume guarantees only at least once semantics. This jira is meant to track exactly once semantics for Flume. My initial idea is to include uuid event ids on events at the original source (use a config to mark a source an original source) and identify destination sinks. At the destination sinks, use a unique ZK Znode to track the events. If once seen (and configured), pull the duplicate out.
> This might need some refactoring, but my belief is we can do this in a backward compatible way.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)