Github user arunmahadevan commented on the issue:
https://github.com/apache/storm/pull/1874
@danny0405 right now rebalance to a higher number of executors is
meaningful only if a component was provisioned with more number of tasks than
executors during deploy time.
May be there is a reason why the number of tasks as not changed with
rebalance. Say if the tasks are maintaining some local state and the inputs to
the tasks are keyed on a field and the rebalance alters the number of tasks,
the states will not be valid anymore since the same keys will not be mapped to
the same tasks anymore.
The idea of dynamically increasing the tasks with rebalance is good, but we
need to think through how to handle the key based partitioning use cases.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
