Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1406#issuecomment-217794597
For addressing big picture of metrics improvement, yes we want to address
four major points.
But given that we already released major version of Storm 1.0.0, we would
want to keep backward compatibility for 1.x. That's why I'm addressing small
improvements first instead of working long-term huge improvements. It's also
planned to phase 2 on JStorm merger in 2.0.0.
But if we have many ideas which relies on that improvements, I think we can
discuss how to address and work on that right now. (evaluation of many ways
including porting metrics feature of JStorm)
Btw, since we're having alternative (Pacemaker) now, we may feel OK to add
small amount of payload to heartbeat message.
If it doesn't make sense, even we can separate heartbeat message and
metrics message, and set frequency of latter thing to 10s or even longer, I
guess we can reduce ZK write load greatly. (since it aggregates built-in
topology metrics and writes to ZK every 3 seconds by default.)
---
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.
---
