You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@storm.apache.org by Rahul Reddy <Ra...@match.com> on 2015/02/23 17:35:56 UTC

Question About Emitted, Transferred and Acked Bolts

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

Re: Question About Emitted, Transferred and Acked Bolts

Posted by Jason Kania <ja...@ymail.com>.

Nathan,
I only get spout failures. None of my bolts fail. Are all failures on a spout going to be associated with timeout? If not, how would one know the difference? Hence my question about whether it would be possible to track timed-out acks explicitly.
Thanks,
Jason

From: Nathan Leung <nc...@gmail.com>
To: user <us...@storm.apache.org>; Jason Kania <ja...@ymail.com>
Sent: Monday, February 23, 2015 4:52 PM
Subject: Re: Question About Emitted, Transferred and Acked Bolts

If your processing takes a long time they may be timing out.

On Mon, Feb 23, 2015 at 4:35 PM, Jason Kania <ja...@ymail.com> wrote:

Thanks for the suggestion. My traffic is only one or two tuples per second in the current environment so I would not expect that to be the problem. I do have failures. Hence, I was wondering if slow acking was the problem. In stepping through the processing, I know the failures aren't in the bolts themselves. That is why I thought it strange.
From: Michael Rose <mi...@fullcontact.com>
To: "user@storm.apache.org" <us...@storm.apache.org>; Jason Kania <ja...@ymail.com>
Sent: Monday, February 23, 2015 4:24 PM
Subject: Re: Question About Emitted, Transferred and Acked Bolts

Do you have enough ackers to keep up with your traffic? How about failures?
Michael RoseSenior Software EngineerFullContact | fullcontact.comm: +1.720.837.1357 | t: @xorlev

All Your Contacts, Updated and In One Place.Try FullContact for Free

On Mon, Feb 23, 2015 at 2:16 PM, Jason Kania <ja...@ymail.com> wrote:

Michael,
That's good to know. I was unaware. That said, if execution of a bolt has not occurred, I would still expect a 0 emit count and acks not to be falling behind the emits by much. My acks are half my emits.
From: Michael Rose <mi...@fullcontact.com>
To: "user@storm.apache.org" <us...@storm.apache.org>; Jason Kania <ja...@ymail.com>
Sent: Monday, February 23, 2015 3:52 PM
Subject: Re: Question About Emitted, Transferred and Acked Bolts

Keep in mind that those metrics are sampled at the rate of topology.stats.sample.rate, 0.05 by default. If you turn it up to 1.0 you'll see full-resolution, though at the price of more time spent collecting metrics.
Michael RoseSenior Software EngineerFullContact | fullcontact.comm: +1.720.837.1357 | t: @xorlev

All Your Contacts, Updated and In One Place.Try FullContact for Free

On Mon, Feb 23, 2015 at 12:14 PM, Jason Kania <ja...@ymail.com> wrote:

I have two comments to add:
1) Is there any JIRA for invalid metrics values? I did not see one. I am running with bolts having breakpoints and long before my bolts are every entered, the metrics indicate that these bolts already have more than 100 emits. I have thought to raise a JIRA on this but I am not sure what I would add for details. Would some specific debug output aid in resolving this?

2) For acks, is there any possibility of adding tracking for acks that happen after a timeout? I can step into my bolt each time it is called and confirm that it is acking each request, yet the acks do not match the emits (which should have a 1 to 1 ratio). I am guessing that this is because the ack happened too late or it might be incorrect metrics total.

I use the STORM UI for processing tracking.

Thanks,
Jason
From: Nathan Leung <nc...@gmail.com>
To: user <us...@storm.apache.org>
Sent: Monday, February 23, 2015 11:56 AM
Subject: Re: Question About Emitted, Transferred and Acked Bolts

executed = # of times you called executedacked = # of executed tuples that you acked; ideally this will match executedemitted = # of tuples that you emitted; if you call emit more than once per execute call this can be higher than execute counttransferred = # 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 <Ra...@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 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

Re: Question About Emitted, Transferred and Acked Bolts

Posted by Nathan Leung <nc...@gmail.com>.

If your processing takes a long time they may be timing out.

On Mon, Feb 23, 2015 at 4:35 PM, Jason Kania <ja...@ymail.com> wrote:

> Thanks for the suggestion. My traffic is only one or two tuples per second
> in the current environment so I would not expect that to be the problem. I
> do have failures. Hence, I was wondering if slow acking was the problem. In
> stepping through the processing, I know the failures aren't in the bolts
> themselves. That is why I thought it strange.
>
>   ------------------------------
>  *From:* Michael Rose <mi...@fullcontact.com>
> *To:* "user@storm.apache.org" <us...@storm.apache.org>; Jason Kania <
> jason.kania@ymail.com>
> *Sent:* Monday, February 23, 2015 4:24 PM
>
> *Subject:* Re: Question About Emitted, Transferred and Acked Bolts
>
> Do you have enough ackers to keep up with your traffic? How about failures?
>
> *Michael Rose*
> Senior Software Engineer
> *Full*Contact | fullcontact.com
> <https://www.fullcontact.com/?utm_source=FullContact%20-%20Email%20Signatures&utm_medium=email&utm_content=Signature%20Link&utm_campaign=FullContact%20-%20Email%20Signatures>
> m: +1.720.837.1357 | t: @xorlev
>
>
> All Your Contacts, Updated and In One Place.
> Try FullContact for Free
> <https://www.fullcontact.com/?utm_source=FullContact%20-%20Email%20Signatures&utm_medium=email&utm_content=Signature%20Link&utm_campaign=FullContact%20-%20Email%20Signatures>
>
>
>
> On Mon, Feb 23, 2015 at 2:16 PM, Jason Kania <ja...@ymail.com>
> wrote:
>
> Michael,
>
> That's good to know. I was unaware. That said, if execution of a bolt has
> not occurred, I would still expect a 0 emit count and acks not to be
> falling behind the emits by much. My acks are half my emits.
>
>   ------------------------------
>  *From:* Michael Rose <mi...@fullcontact.com>
> *To:* "user@storm.apache.org" <us...@storm.apache.org>; Jason Kania <
> jason.kania@ymail.com>
> *Sent:* Monday, February 23, 2015 3:52 PM
>
> *Subject:* Re: Question About Emitted, Transferred and Acked Bolts
>
> Keep in mind that those metrics are sampled at the rate
> of topology.stats.sample.rate, 0.05 by default. If you turn it up to 1.0
> you'll see full-resolution, though at the price of more time spent
> collecting metrics.
>
> *Michael Rose*
> Senior Software Engineer
> *Full*Contact | fullcontact.com
> <https://www.fullcontact.com/?utm_source=FullContact%20-%20Email%20Signatures&utm_medium=email&utm_content=Signature%20Link&utm_campaign=FullContact%20-%20Email%20Signatures>
> m: +1.720.837.1357 | t: @xorlev
>
>
> All Your Contacts, Updated and In One Place.
> Try FullContact for Free
> <https://www.fullcontact.com/?utm_source=FullContact%20-%20Email%20Signatures&utm_medium=email&utm_content=Signature%20Link&utm_campaign=FullContact%20-%20Email%20Signatures>
>
>
>
> On Mon, Feb 23, 2015 at 12:14 PM, Jason Kania <ja...@ymail.com>
> wrote:
>
> I have two comments to add:
>
> 1) Is there any JIRA for invalid metrics values? I did not see one. I am
> running with bolts having breakpoints and long before my bolts are every
> entered, the metrics indicate that these bolts already have more than 100
> emits. I have thought to raise a JIRA on this but I am not sure what I
> would add for details. Would some specific debug output aid in resolving
> this?
>
> 2) For acks, is there any possibility of adding tracking for acks that
> happen after a timeout? I can step into my bolt each time it is called and
> confirm that it is acking each request, yet the acks do not match the emits
> (which should have a 1 to 1 ratio). I am guessing that this is because the
> ack happened too late or it might be incorrect metrics total.
>
> I use the STORM UI for processing tracking.
>
> Thanks,
>
> Jason
>
>   ------------------------------
>  *From:* Nathan Leung <nc...@gmail.com>
> *To:* user <us...@storm.apache.org>
> *Sent:* Monday, February 23, 2015 11:56 AM
> *Subject:* Re: Question About Emitted, Transferred and Acked Bolts
>
> 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 <Ra...@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
> 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
>
>
>
>
>
>
>
>
>
>
>

Re: Question About Emitted, Transferred and Acked Bolts

Posted by Jason Kania <ja...@ymail.com>.

Do you have enough ackers to keep up with your traffic? How about failures?
Michael RoseSenior Software EngineerFullContact | fullcontact.comm: +1.720.837.1357 | t: @xorlev

All Your Contacts, Updated and In One Place.Try FullContact for Free

On Mon, Feb 23, 2015 at 2:16 PM, Jason Kania <ja...@ymail.com> wrote:

All Your Contacts, Updated and In One Place.Try FullContact for Free

On Mon, Feb 23, 2015 at 12:14 PM, Jason Kania <ja...@ymail.com> wrote:

I use the STORM UI for processing tracking.

Thanks,
Jason
From: Nathan Leung <nc...@gmail.com>
To: user <us...@storm.apache.org>
Sent: Monday, February 23, 2015 11:56 AM
Subject: Re: Question About Emitted, Transferred and Acked Bolts

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

Hi,

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

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

Thanks
Rahul

Re: Question About Emitted, Transferred and Acked Bolts

Posted by Michael Rose <mi...@fullcontact.com>.

Do you have enough ackers to keep up with your traffic? How about failures?

*Michael Rose*
Senior Software Engineer
*Full*Contact | fullcontact.com
<https://www.fullcontact.com/?utm_source=FullContact%20-%20Email%20Signatures&utm_medium=email&utm_content=Signature%20Link&utm_campaign=FullContact%20-%20Email%20Signatures>
m: +1.720.837.1357 | t: @xorlev


All Your Contacts, Updated and In One Place.
Try FullContact for Free
<https://www.fullcontact.com/?utm_source=FullContact%20-%20Email%20Signatures&utm_medium=email&utm_content=Signature%20Link&utm_campaign=FullContact%20-%20Email%20Signatures>

On Mon, Feb 23, 2015 at 2:16 PM, Jason Kania <ja...@ymail.com> wrote:

> Michael,
>
> That's good to know. I was unaware. That said, if execution of a bolt has
> not occurred, I would still expect a 0 emit count and acks not to be
> falling behind the emits by much. My acks are half my emits.
>
>   ------------------------------
>  *From:* Michael Rose <mi...@fullcontact.com>
> *To:* "user@storm.apache.org" <us...@storm.apache.org>; Jason Kania <
> jason.kania@ymail.com>
> *Sent:* Monday, February 23, 2015 3:52 PM
>
> *Subject:* Re: Question About Emitted, Transferred and Acked Bolts
>
> Keep in mind that those metrics are sampled at the rate
> of topology.stats.sample.rate, 0.05 by default. If you turn it up to 1.0
> you'll see full-resolution, though at the price of more time spent
> collecting metrics.
>
> *Michael Rose*
> Senior Software Engineer
> *Full*Contact | fullcontact.com
> <https://www.fullcontact.com/?utm_source=FullContact%20-%20Email%20Signatures&utm_medium=email&utm_content=Signature%20Link&utm_campaign=FullContact%20-%20Email%20Signatures>
> m: +1.720.837.1357 | t: @xorlev
>
>
> All Your Contacts, Updated and In One Place.
> Try FullContact for Free
> <https://www.fullcontact.com/?utm_source=FullContact%20-%20Email%20Signatures&utm_medium=email&utm_content=Signature%20Link&utm_campaign=FullContact%20-%20Email%20Signatures>
>
>
>
> On Mon, Feb 23, 2015 at 12:14 PM, Jason Kania <ja...@ymail.com>
> wrote:
>
> I have two comments to add:
>
> 1) Is there any JIRA for invalid metrics values? I did not see one. I am
> running with bolts having breakpoints and long before my bolts are every
> entered, the metrics indicate that these bolts already have more than 100
> emits. I have thought to raise a JIRA on this but I am not sure what I
> would add for details. Would some specific debug output aid in resolving
> this?
>
> 2) For acks, is there any possibility of adding tracking for acks that
> happen after a timeout? I can step into my bolt each time it is called and
> confirm that it is acking each request, yet the acks do not match the emits
> (which should have a 1 to 1 ratio). I am guessing that this is because the
> ack happened too late or it might be incorrect metrics total.
>
> I use the STORM UI for processing tracking.
>
> Thanks,
>
> Jason
>
>   ------------------------------
>  *From:* Nathan Leung <nc...@gmail.com>
> *To:* user <us...@storm.apache.org>
> *Sent:* Monday, February 23, 2015 11:56 AM
> *Subject:* Re: Question About Emitted, Transferred and Acked Bolts
>
> 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 <Ra...@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
> 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
>
>
>
>
>
>
>
>

Re: Question About Emitted, Transferred and Acked Bolts

Posted by Jason Kania <ja...@ymail.com>.

All Your Contacts, Updated and In One Place.Try FullContact for Free

On Mon, Feb 23, 2015 at 12:14 PM, Jason Kania <ja...@ymail.com> wrote:

I use the STORM UI for processing tracking.

Thanks,
Jason
From: Nathan Leung <nc...@gmail.com>
To: user <us...@storm.apache.org>
Sent: Monday, February 23, 2015 11:56 AM
Subject: Re: Question About Emitted, Transferred and Acked Bolts

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

Hi,

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

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

Thanks
Rahul

Re: Question About Emitted, Transferred and Acked Bolts

Posted by Michael Rose <mi...@fullcontact.com>.

Keep in mind that those metrics are sampled at the rate
of topology.stats.sample.rate, 0.05 by default. If you turn it up to 1.0
you'll see full-resolution, though at the price of more time spent
collecting metrics.

*Michael Rose*
Senior Software Engineer
*Full*Contact | fullcontact.com
<https://www.fullcontact.com/?utm_source=FullContact%20-%20Email%20Signatures&utm_medium=email&utm_content=Signature%20Link&utm_campaign=FullContact%20-%20Email%20Signatures>
m: +1.720.837.1357 | t: @xorlev


All Your Contacts, Updated and In One Place.
Try FullContact for Free
<https://www.fullcontact.com/?utm_source=FullContact%20-%20Email%20Signatures&utm_medium=email&utm_content=Signature%20Link&utm_campaign=FullContact%20-%20Email%20Signatures>

On Mon, Feb 23, 2015 at 12:14 PM, Jason Kania <ja...@ymail.com> wrote:

> I have two comments to add:
>
> 1) Is there any JIRA for invalid metrics values? I did not see one. I am
> running with bolts having breakpoints and long before my bolts are every
> entered, the metrics indicate that these bolts already have more than 100
> emits. I have thought to raise a JIRA on this but I am not sure what I
> would add for details. Would some specific debug output aid in resolving
> this?
>
> 2) For acks, is there any possibility of adding tracking for acks that
> happen after a timeout? I can step into my bolt each time it is called and
> confirm that it is acking each request, yet the acks do not match the emits
> (which should have a 1 to 1 ratio). I am guessing that this is because the
> ack happened too late or it might be incorrect metrics total.
>
> I use the STORM UI for processing tracking.
>
> Thanks,
>
> Jason
>
>   ------------------------------
>  *From:* Nathan Leung <nc...@gmail.com>
> *To:* user <us...@storm.apache.org>
> *Sent:* Monday, February 23, 2015 11:56 AM
> *Subject:* Re: Question About Emitted, Transferred and Acked Bolts
>
> 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 <Ra...@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
> 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
>
>
>
>
>

Re: Question About Emitted, Transferred and Acked Bolts

Posted by Jason Kania <ja...@ymail.com>.

I use the STORM UI for processing tracking.

Thanks,
Jason
From: Nathan Leung <nc...@gmail.com>
To: user <us...@storm.apache.org>
Sent: Monday, February 23, 2015 11:56 AM
Subject: Re: Question About Emitted, Transferred and Acked Bolts

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

Hi,

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

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

Thanks
Rahul

Re: Question About Emitted, Transferred and Acked Bolts

Posted by Nathan Leung <nc...@gmail.com>.

As Michael noted these values are sampled (by default) and are therefore
not precise.  If they are close to each other (within 20, possibly more
depending on your traffic) they are probably the same.  If you are really
not acking tuples (the ack value is really lower) you will see failures at
the spout increase.  In practice I cannot think of any scenario where you
would have more acks than executes in your bolt.

On Fri, Feb 27, 2015 at 2:16 AM, Shivendra Singh <SS...@walmartlabs.com>
wrote:

> Hi Nathan,
>
> I have more acked than executed for some bolts and reverse in others. In
> what scenario will this happen?
>
> Regards,
> Shivendra
>
> From: Nathan Leung <nc...@gmail.com>>
> Reply-To: "user@storm.apache.org<ma...@storm.apache.org>" <
> user@storm.apache.org<ma...@storm.apache.org>>
> Date: Monday, February 23, 2015 at 8:56 AM
> To: user <us...@storm.apache.org>>
> Subject: Re: Question About Emitted, Transferred and Acked Bolts
>
> 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 <Rahul.Reddy@match.com
> <ma...@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
> 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
>
>
>

Re: Question About Emitted, Transferred and Acked Bolts

Posted by Shivendra Singh <SS...@walmartlabs.com>.

Hi Nathan,

I have more acked than executed for some bolts and reverse in others. In what scenario will this happen?

Regards,
Shivendra

From: Nathan Leung <nc...@gmail.com>>
Reply-To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Date: Monday, February 23, 2015 at 8:56 AM
To: user <us...@storm.apache.org>>
Subject: Re: Question About Emitted, Transferred and Acked Bolts

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 <Ra...@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 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

Re: Question About Emitted, Transferred and Acked Bolts

Posted by Nathan Leung <nc...@gmail.com>.

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 <Ra...@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
> 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
>
>