Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/1132#issuecomment-187040728
I am thinking of the side effects that this change can lead to -
1. Number of tasks could be more than number of partitions - Acceptable and
will be corrected in next refresh
2. GlobalPartitionMapping may be different for multiple tasks - Depending
on when the spout task reads the kafka cluster zookeeper, it is possible that
task A reads 15 partitions and task B reads 16 partitions for a topic with
total 16 partitions. This can be problematic as it will lead to two tasks
assigning same partitions to themselves. It breaks the contract that same
partition won't be read by two different tasks.
---
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.
---
