Return-Path: 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 7B9CE184BC for ; Mon, 6 Jul 2015 05:14:50 +0000 (UTC) Received: (qmail 24492 invoked by uid 500); 6 Jul 2015 05:14:50 -0000 Delivered-To: apmail-flume-user-archive@flume.apache.org Received: (qmail 24429 invoked by uid 500); 6 Jul 2015 05:14:50 -0000 Mailing-List: contact user-help@flume.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flume.apache.org Delivered-To: mailing list user@flume.apache.org Received: (qmail 24419 invoked by uid 99); 6 Jul 2015 05:14:50 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jul 2015 05:14:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 8D1BF18291F for ; Mon, 6 Jul 2015 05:14:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id pah8u1JOltNe for ; Mon, 6 Jul 2015 05:14:37 +0000 (UTC) Received: from mail-wg0-f41.google.com (mail-wg0-f41.google.com [74.125.82.41]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 5A14E428CC for ; Mon, 6 Jul 2015 05:14:37 +0000 (UTC) Received: by wgqq4 with SMTP id q4so129854996wgq.1 for ; Sun, 05 Jul 2015 22:14:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=EOMEyfnMMU3+2ieKv9v89wy8t1t14ZvPJfC11diyWLQ=; b=VhbzIiURHN8OVYsxCAwKasujdUV9NkhPCbbxxXu4oV7UaCjV7l7R1pX80LaxY8KBWQ 4jTF5flT8dyKk3eK7VIHpPfKQK+3BKdLLrJTLnp/VZAABFa/OLdxgYQnJWjueM6O295E N65fuDFY3g2r9iXww/JWRhSQx906DiugOvBuObJatSerSd3C65dBxvMiHZXZHjb4VGUI VRhAAHR6/VroobHd9LMBCSbPrruna41Lekohhuyyxxw5xkcZIe79i+H5kcnp2a4oB9tq KhQYcLbmIQz7suEaApi4WUuvQ75xmaaAFiAnj/chKTG5//F1O1a3YwP5WSTE6d4HE1/C +YNg== X-Gm-Message-State: ALoCoQlJJtrV+h7d2+HPlzngPxD3WcN/IjV9PboDcHc1gv/msP/O2lpvDz0BI0CewOq0/KCyEQ3X MIME-Version: 1.0 X-Received: by 10.194.82.167 with SMTP id j7mr92430616wjy.123.1436159676346; Sun, 05 Jul 2015 22:14:36 -0700 (PDT) Received: by 10.27.139.212 with HTTP; Sun, 5 Jul 2015 22:14:36 -0700 (PDT) In-Reply-To: <54F40977-4B8B-4033-BD37-6E88F371CD8D@gmail.com> References: <5C07F644-F9B2-4584-8663-82C768B1BE1B@gmail.com> <54F40977-4B8B-4033-BD37-6E88F371CD8D@gmail.com> Date: Sun, 5 Jul 2015 22:14:36 -0700 Message-ID: Subject: Re: Flafka: Kafka channel unable to deliver event From: Gwen Shapira To: user@flume.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable See inline :) On Sun, Jul 5, 2015 at 5:37 PM, Jun MA wrote: > Hi Rufus, > > Thank you so much for your help, I do bypass the issue. > > Another question I have is that can I have two Flafka agents consume from > one topic (agents run on same machine or different machine)? Yes. > Will the two > agents have exact same two copies or each agent will consume one part of = the > topic? It depends on how you configure them. If you configure two different consumer group IDs, they will each get a cop= y. If they use the same consumer group ID, each agent will consume from different subset of partitions. They will automatically load balance partitions in case more agents join or if agents are stopped. > The purpose I want to run two agents on same topic is that I want to > have a high availability. What I want is that two agents will consume > different portion of the topic but if one agent down, the other one will > consume everything from the topic. > From what I tested, I bring up two agents on same machine with different > agent name (everything else are the same), and only the first one can > consume messages from topic. I=E2=80=99m wondering if it is the right beh= avior. If > so, is there anyway I can solve this single point of failure? If you configure both Flafkas with same consumer group ID, you should get the behavior you want. Just make sure you have at least two partitions - the load balancing behavior happens at the partition level, so you can only have as many concurrent agents as you have partitions. Gwen > > Bests, > Jun > > On Jul 4, 2015, at 10:22 AM, Johny Rufus wrote: > > Been looking into this for some time and found a couple of issues. Raised > Jiras for both, there are workarounds to get past these errors. > > https://issues.apache.org/jira/browse/FLUME-2734 > https://issues.apache.org/jira/browse/FLUME-2735 > > For timeout to take effect, you need to specify as - > agent1.channels.channel1.timeout =3D 1000000 (This is a temporary work ar= ound, > kafka.consumer.timeout.ms should work as per the guide when FLUME-2734 is > resolved) > > To get past the IllegalStateException, I had to download the zookeeper ja= r > from http://mvnrepository.com/artifact/org.apache.zookeeper/zookeeper/3.3= .6 > and put it in the lib directory. This is also a workaround to get past th= e > issue, until we figure out the root cause. > > > Thanks, > Rufus > > On Fri, Jul 3, 2015 at 10:09 PM, Jun Ma wrote: >> >> Oops, thanks for figuring that out. >> Any idea why unable to deliver event? >> >> On Fri, Jul 3, 2015 at 8:00 PM, Johny Rufus wrote: >>> >>> There is a typo in your property "cnannel1", hence the property is not >>> set >>> >>> a1.channels.cnannel1.kafka.consumer.timeout.ms =3D 1000000 >>> >>> Thanks, >>> Rufus >>> >>> On Fri, Jul 3, 2015 at 4:49 PM, Jun Ma wrote: >>>> >>>> Thanks for your reply. But from what I read, the magic things Flafka >>>> does is that you don't need to have a source, you can directly move th= ings >>>> from channel to sink. >>>> >>>> http://blog.cloudera.com/blog/2014/11/flafka-apache-flume-meets-apache= -kafka-for-event-processing/ >>>> (see Flume's kafka channel) >>>> >>>> >>>> On Fri, Jul 3, 2015 at 1:26 PM, Foo Lim wrote: >>>>> >>>>> There's an error that you didn't specify a source: >>>>> >>>>> Agent configuration for 'a1' has no sources. >>>> >>>> >>> >> > >