Return-Path: 
 <user-return-3047-apmail-flume-user-archive=flume.apache.org@flume.apache.org>
X-Original-To: apmail-flume-user-archive@www.apache.org
Delivered-To: apmail-flume-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id F2C2FDFFD
	for <apmail-flume-user-archive@www.apache.org>;
 Thu, 13 Dec 2012 05:42:43 +0000 (UTC)
Received: (qmail 56952 invoked by uid 500); 13 Dec 2012 05:42:43 -0000
Delivered-To: apmail-flume-user-archive@flume.apache.org
Received: (qmail 56784 invoked by uid 500); 13 Dec 2012 05:42:41 -0000
Mailing-List: contact user-help@flume.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@flume.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@flume.apache.org>
List-Post: <mailto:user@flume.apache.org>
List-Id: <user.flume.apache.org>
Reply-To: user@flume.apache.org
Delivered-To: mailing list user@flume.apache.org
Received: (qmail 56757 invoked by uid 99); 13 Dec 2012 05:42:40 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 05:42:40 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of guy.peleg@gmail.com
 designates 209.85.215.51 as permitted sender)
Received: from [209.85.215.51] (HELO mail-la0-f51.google.com) (209.85.215.51)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 05:42:34 +0000
Received: by mail-la0-f51.google.com with SMTP id e4so1390165lag.38
        for <user@flume.apache.org>; Wed, 12 Dec 2012 21:42:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=PbqGGS/if8mUqGKqZT5v1SZ1mFGBa0tbU05ON+IBCD8=;
        b=Yojp4Y40wrrpyw9c99DvUJrX61lRZRkKR7Jr5SmB8PlmpF840UIdvcGQoQly/8gGGP
         6RsgRQsPuFMq42yNySrJ3WE+lQVxvPY1EIDsUGE6xX1VKYKLbRRNcOUqzC/83rIVYahZ
         QMObFD9NSxncHHtj+kRBR9Aoejv7Ay/kqLus2fmQlXsC3FuboZmfcVfCRyofRFrrrhwc
         RDLA29LG3w//7R1K/LlyxM3k53UUm92BTMDNtYVub39ONobC/+h8OpviH5kx443DUTpM
         00rqY8IfqD7G0NQVLt++QRmzAJ2t55oD9lgtKVooXrr0nTBxwPNARSCTVNi8WVzx3NPB
         Kn0w==
MIME-Version: 1.0
Received: by 10.112.85.35 with SMTP id e3mr368121lbz.106.1355377332629; Wed,
 12 Dec 2012 21:42:12 -0800 (PST)
Received: by 10.152.132.105 with HTTP; Wed, 12 Dec 2012 21:42:12 -0800 (PST)
Date: Thu, 13 Dec 2012 07:42:12 +0200
Message-ID: 
 <CAMX9-RrhmaenUqT+wx84vf_NZ2LX89b0_gxR5LxA+8LM+4HJfQ@mail.gmail.com>
Subject: Reliable delivery of the events
From: Guy Peleg <guy.peleg@gmail.com>
To: user@flume.apache.org
Content-Type: multipart/alternative; boundary=bcaec555557c72b15e04d0b56088
X-Virus-Checked: Checked by ClamAV on apache.org

--bcaec555557c72b15e04d0b56088
Content-Type: text/plain; charset=ISO-8859-1

Hi,

>From the documentation: "Flume uses a transactional approach to guarantee
the reliable delivery of the events"

But if I have a multi-hope flow, and the first agent crashes before the
message received from the client was stored on the channel then the message
is lost since the client is not synched with Flume-NG transaction
mechanism, is that correct?

Thanks,

Guy

--bcaec555557c72b15e04d0b56088
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>From the=A0documentation: &quot;<sp=
an style=3D"background-color:rgb(255,255,255);font-family:sans-serif;font-s=
ize:16px;line-height:20.799999237060547px;text-align:justify">Flume uses a =
transactional approach to guarantee the reliable delivery of the events&quo=
t;</span></div>
<div><span style=3D"background-color:rgb(255,255,255);font-family:sans-seri=
f;font-size:16px;line-height:20.799999237060547px;text-align:justify"><br><=
/span></div><div>But if I have a multi-hope flow, and the first agent crash=
es before the message received from the client was stored on the channel th=
en the message is lost since the client is not synched with Flume-NG transa=
ction mechanism, is that correct?</div>
<div><br></div><div>Thanks,</div><div><br></div><div>Guy</div><div><br></di=
v><div><br></div></div>

--bcaec555557c72b15e04d0b56088--