Return-Path: 
 <user-return-5348-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 BC3391042E
	for <apmail-flume-user-archive@www.apache.org>;
 Tue, 18 Mar 2014 00:39:02 +0000 (UTC)
Received: (qmail 36554 invoked by uid 500); 18 Mar 2014 00:39:01 -0000
Delivered-To: apmail-flume-user-archive@flume.apache.org
Received: (qmail 36429 invoked by uid 500); 18 Mar 2014 00:39:00 -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 36419 invoked by uid 99); 18 Mar 2014 00:39:00 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2014 00:39:00 +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 jimmyjack@gmail.com
 designates 209.85.220.181 as permitted sender)
Received: from [209.85.220.181] (HELO mail-vc0-f181.google.com)
 (209.85.220.181)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2014 00:38:55 +0000
Received: by mail-vc0-f181.google.com with SMTP id id10so6351825vcb.26
        for <user@flume.apache.org>; Mon, 17 Mar 2014 17:38:34 -0700 (PDT)
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=Fjaa4UxnESNViRQpy9+15igWXmcVoZk1lrhHNC4FHoc=;
        b=r7a/hIxzwGp8kXg3AcRYVsZFuhCuHXHce72NrUKIrrPbaDl42g+mAYDhk8ipelcDIa
         r5mrk/GqGxO16lXwrIs/haGDIlX2Nj1YWiErRXEPXMr/ySPoKX7Nh4JKENFY9pZ2DxqC
         3Es1kV90hp9r27t5axT6fDlTwGMdsR3GgqHUUpHON3Z6xn1mOCDe0cGU+p/E5chP4neA
         wvW3uhLIzPfDH8YrZa7piE+CLAxRU6mc6kWLuESjAEAm/jZECcmsBP08bOaJweAFwiIl
         eVHSK4C2rqEV7tKGC+9PBPz3ky5o1vLMjzlzPFwBh5Hh14Czwbsjr9+bJkNHwYyXMYQ+
         KC4w==
MIME-Version: 1.0
X-Received: by 10.52.241.106 with SMTP id wh10mr18765102vdc.16.1395103114353;
 Mon, 17 Mar 2014 17:38:34 -0700 (PDT)
Received: by 10.220.155.139 with HTTP; Mon, 17 Mar 2014 17:38:34 -0700 (PDT)
Date: Mon, 17 Mar 2014 17:38:34 -0700
Message-ID: 
 <CAE0GdZVUVfuQ70pg++65+-Gum8znovhVkg11G4L9AsWqF-35=A@mail.gmail.com>
Subject: JMS source and full file channel
From: Jimmy <jimmyjack@gmail.com>
To: user@flume.apache.org
Content-Type: multipart/alternative; boundary=001a1133eb388e615a04f4d6c1af
X-Virus-Checked: Checked by ClamAV on apache.org

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

I have JMS source and file channel with HDFS sink... so far works good

lets assume I hit channel capacity (for whatever reason e.g. HDFS down) and
channel stops accepting new messages from source....

JMS is going to pull a message from queue and will try to delivery to
channel, but cannot, it will rollback. Again, works...

Now if the channel is full for a while, am I going to see JMS pulling
messages from queue like crazy monkey just to roll them back few ms later
or is there some timeout-retry window e.g. "if JMS source cannot delivery 3
messages to channel, wait 30 seconds they retry again"

thank you

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

<div dir=3D"ltr">I have JMS source and file channel with HDFS sink... so fa=
r works good<div><br></div><div>lets assume I hit channel capacity (for wha=
tever reason e.g. HDFS down) and channel stops accepting new messages from =
source....</div>
<div><br></div><div>JMS is going to pull a message from queue and will try =
to delivery to channel, but cannot, it will rollback. Again, works...</div>=
<div><br></div><div>Now if the channel is full for a while, am I going to s=
ee JMS pulling messages from queue like crazy monkey just to roll them back=
 few ms later or is there some timeout-retry window e.g. &quot;if JMS sourc=
e cannot delivery 3 messages to channel, wait 30 seconds they retry again&q=
uot;</div>
<div><br></div><div>thank you</div><div><br></div><div><br></div><div><br><=
/div></div>

--001a1133eb388e615a04f4d6c1af--