Abhishek Agarwal created STORM-972:
--------------------------------------
Summary: Metrics logging frequency should not be affected with
bolt execute slowness
Key: STORM-972
URL: https://issues.apache.org/jira/browse/STORM-972
Project: Apache Storm
Issue Type: Improvement
Reporter: Abhishek Agarwal
I had registered metrics in my bolt for 60 seconds, but I noticed that they
were not getting logged even after two minutes. After running the topology for
a while, bolt metrics were logged eventually but not according to the
metricBucketSizeInSecs. System inbuilt metrics were working just fine.
Bolt actually sends the metrics to the consumer bolt, only after it receives
the metric tick tuple for processing. Even though the tick was generated after
60 seconds, it is sent in the same queue along with messages from spout. Bolt
will see the tick only after processing messages from spout, which could be any
duration.
If this diagnosis is correct, can we just for metric interval lapse in a loop
instead of relying on metric tick. I suppose this problem only exists for the
bolt.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
