Details
-
Bug
-
Status: Open
-
Critical
-
Resolution: Unresolved
-
2.0.0
-
None
-
None
Description
Possible overscheduling captured when follow steps are performed (Logging is added in STORM-3147)
1) launch nimbus & zookeeper
2) launch supervisor 1
3) launch topology 1 (I used org.apache.storm.starter.WordCountTopology)
4) launch supervisor 2
5) launch topology 2 (I used org.apache.storm.starter.ExclamationTopology)
2018-07-13 12:58:43.196 o.a.s.d.n.Nimbus timer [WARN] Memory over-scheduled on 176ec6d4-2df3-40ca-95ca-c84a81dbcc22-172.130.97.212
Indicating there may be issues inside scheduler.
It is discovered when I ported ClusterSummay to StormMetrics
Attachments
Issue Links
- relates to
-
STORM-3147 Port ClusterSummary as Metrics to StormMetricsRegistry
- Resolved