Thanks Haohui to share your thoughts. Let me add some comments inline.
2016년 10월 13일 (목) 오후 2:31, Haohui Mai 님이 작성:
Please allow me to share some of the thoughts on this front:
1. The concepts of monotonic primary key is ensure forward progress for the
query from the
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1736
Just fixed the RAT issue.
---
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
Ok, so even JmxPreparableReporter does not give any more metrics about the
workers.
The only way to get the metrics for spouts/bolts/topologies is non-JMX -
staslev-metrics-reporter or the verisign-metrics-reporter.
-T.I.
On Fri, Oct 14, 2016 at 7:42 AM, Kishorkumar Patil <
Alessandro,
One caution is "num-getClusterInfo-calls" is not strictly number of thrift
calls but # of times method was invoked. We do not have separate thrift entry
method from rest of the internal calls to getClusterInfo
Regards,
-Kishor
On Friday, October 14, 2016 8:31 AM, Alessandro
T.I.
I ran jconsole and ended up with the same result for a worker.
That said, if you turn on JMX for the daemons you end up with a new MBean
"metrics" (as given by storm.daemon.metrics.reporter.plugin.domain). This is
coming from: JmxPreparableReporter.
- For nimbus I see stuff like:
GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/storm/pull/1736
STORM-1446 Compile the Calcite logical plan to Storm Trident logical plan
First of all I should thank to @milinda for sharing great implementation,
because this patch is merely just a port of