jiajunwang opened a new issue #1255: URL: https://github.com/apache/helix/issues/1255
**Describe the bug** There is a regression in the WAGED Change Detector. The detector ignores IS list field key changes. In this case, the rebalancer won't trigger the required rebalance. As a result, the newly added resource or new partitions won't be assigned automatically. **To Reproduce** Call HelixAdmin.addResource() to add a new resource. Wait for a while, until the first rebalance is done. Call HelixAdmin.rebalance() for the new resource. Ideally, the admin will update the IS with a fully extended partition list. And the rebalancer should assign the partitions. However, due to the regression, this 2nd change will not trigger the baseline rebalance. So the new partitions won't be assigned. **Expected behavior** After HelixAdmin.rebalance() called, all the partitions of this new resource should be assigned shortly, and automatically. **Additional context** Impacted Version: 1.0.1 This bug only impacts WAGED managed resources. As a workaround, manually trigger rebalance (for example, touching the IdealState by changing the NUM_PARTITIONS and then changing it back), or reset the helix controller to trigger a refresh baseline rebalance. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
