[ https://issues.apache.org/jira/browse/STORM-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545742#comment-16545742 ]
Jungtaek Lim commented on STORM-3151: ------------------------------------- We're using "Fix version/s" as actual fix version, so it should be set when patch is going to be merged in. > Negative Scheduling Resource/Overscheduling issue > ------------------------------------------------- > > Key: STORM-3151 > URL: https://issues.apache.org/jira/browse/STORM-3151 > Project: Apache Storm > Issue Type: Bug > Components: storm-server > Affects Versions: 2.0.0 > Reporter: Zhengdai Hu > Priority: Critical > > 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) > {noformat} > 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 > {noformat} > Indicating there may be issues inside scheduler. > It is discovered when I ported ClusterSummay to StormMetrics -- This message was sent by Atlassian JIRA (v7.6.3#76005)