Hi, Now the executor can deal with a range of tasks. However, I cannot get the advantage of this design. If we simplify the design, we can get a more clear execution model and more clear scheduler (such as optimized for the most frequent shuffleGrouping).
If you think this idea can be useful for Storm, I will create a JIRA for that and have a try to disable the setNumTasks interface. Maybe another simple scheduler can be tried. Looking forward to some suggestion. Thanks.
