From user-return-6253-apmail-storm-user-archive=storm.apache.org@storm.apache.org Mon Feb 23 16:57:30 2015 Return-Path: X-Original-To: apmail-storm-user-archive@minotaur.apache.org Delivered-To: apmail-storm-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 82D4210AC7 for ; Mon, 23 Feb 2015 16:57:30 +0000 (UTC) Received: (qmail 73500 invoked by uid 500); 23 Feb 2015 16:57:17 -0000 Delivered-To: apmail-storm-user-archive@storm.apache.org Received: (qmail 73456 invoked by uid 500); 23 Feb 2015 16:57:17 -0000 Mailing-List: contact user-help@storm.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.apache.org Delivered-To: mailing list user@storm.apache.org Received: (qmail 73445 invoked by uid 99); 23 Feb 2015 16:57:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Feb 2015 16:57:17 +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 (nike.apache.org: domain of ncleung@gmail.com designates 209.85.213.181 as permitted sender) Received: from [209.85.213.181] (HELO mail-ig0-f181.google.com) (209.85.213.181) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Feb 2015 16:56:52 +0000 Received: by mail-ig0-f181.google.com with SMTP id hn18so19778442igb.2 for ; Mon, 23 Feb 2015 08:56:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=k10B0I4D+ohGpw7OLm0teYaQ5tbUwryJShF1/wG+XCc=; b=zfTPAPo6isbdnZwdb6odMvqjr+KrdTrcmymMAvn0giBDO0aktGnet9bA27a/ZTR6Sv OAHWdfWFcFSzxg5UDswYe/uoTZEF4pm6XDdGZ+qTCUZLoSoD2ehza+QnYPrpEEsYPSAY YsW3B1U3RaUeI0sDmm0ZDZ1+zpBwzczhMHMWmi9LvmE6giraO7bOfVjjdD47MFezlDkD cb9cNZIstSslqRFSdH0umnyVg5DVLC5jtLlsPYeP1GokIN89voTZ1+tsFb2rk7T8MSDV yI8m7x0xgVgpcT83Z3BKuVGJaEOU1UpeRWV8IITYAoYBHDdmg/QH5W2ra+cPgMK3/Fhw rXJg== MIME-Version: 1.0 X-Received: by 10.42.39.147 with SMTP id h19mr12323122ice.91.1424710565611; Mon, 23 Feb 2015 08:56:05 -0800 (PST) Received: by 10.64.19.110 with HTTP; Mon, 23 Feb 2015 08:56:05 -0800 (PST) In-Reply-To: References: Date: Mon, 23 Feb 2015 11:56:05 -0500 Message-ID: Subject: Re: Question About Emitted, Transferred and Acked Bolts From: Nathan Leung To: user Content-Type: multipart/alternative; boundary=90e6ba61464c2bf114050fc4473f X-Virus-Checked: Checked by ClamAV on apache.org --90e6ba61464c2bf114050fc4473f Content-Type: text/plain; charset=UTF-8 executed = # of times you called executed acked = # of executed tuples that you acked; ideally this will match executed emitted = # of tuples that you emitted; if you call emit more than once per execute call this can be higher than execute count transferred = # of tuples transferred downstream; if you have 2 bolts subscribing to your bolt, then this count can be higher than emitted. On Mon, Feb 23, 2015 at 11:35 AM, Rahul Reddy wrote: > Hi, > > Can you guys help me understand difference between emitted, transferred > and acked tuples. > > In my case every tuple emitted by ablog-filter-bolt will be processed by > ablog-flatten-xml-bolt which will then be written by ablog-hdfs-bolt to > hdfs. Ideally all metrics for executed/acked should match after tuples are > emitted from ablog-filter-bolt . I'm not sure why there is so much > discrepancy in emitted/transferredacked tuple count between these bolts > although it dosent show any failed tuples. > > Any ideas what I can check and how to interpret metrics correctly? > > Thanks > Rahul > > --90e6ba61464c2bf114050fc4473f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
executed =3D # of times you called executed
acked =3D = # of executed tuples that you acked; ideally this will match executed
=
emitted =3D # of tuples that you emitted; if you call emit more than o= nce per execute call this can be higher than execute count
transf= erred =3D # of tuples transferred downstream; if you have 2 bolts subscribi= ng to your bolt, then this count can be higher than emitted.

On Mon, Feb 23, 2015= at 11:35 AM, Rahul Reddy <Rahul.Reddy@match.com> wrote:=
Hi,

Can you guys help me understand difference between emitted, transferred and= acked tuples.

In my case every tuple emitted by ablog-filter-bolt will be processed by ab= log-flatten-xml-bolt which will then be written by ablog-hdfs-bolt to hdfs.= Ideally all metrics for executed/acked should match after tuples are emitt= ed from ablog-filter-bolt . I'm not sure why there is so much discrepan= cy in emitted/transferredacked tuple count between these bolts although it = dosent show any failed tuples.

Any ideas what I can check and how to interpret metrics correctly?

Thanks
Rahul


--90e6ba61464c2bf114050fc4473f--