Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1322#issuecomment-207251473
@abhishekagarwal87
Yes, I also have two ideas to avoid or minimize those issues.
1) discard policy
2) filter metrics
About 1) _taskQueue will become bounded queue. And when it's full, we
discard some enqueued tasks via policy. Policy could be drop oldest, drop
latest, drop randomly, or even provide interface for plug-in.
About 2), actually there're many metrics provided by Storm by default.
Furthermore, some modules like storm-kafka provides their metrics, too. If
users set pattern what they want to subscribe or filter out that would be great.
I'm going to create an umbrella issue regarding improvement of metrics and
add STORM-1698 as subtask.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
