ngngwr opened a new issue, #3077:
URL: https://github.com/apache/helix/issues/3077
### Describe the bug
When the resource gets deleted midway by customer scripts/externally after
(!_zkClient.exists(zkPath)) check and another process is trying to update the
deleted resource's idealstate. The resource gets created with just the updated
parameters in the API payload.
This can lead to rebalance failure as well when the updated parameters does
not contain the num of partitions. Rebalancer considers num_partition for this
resource as -1 leading to rebalance failure.
### To Reproduce
- Start helix rest in debug mode. Trigger update ideal state API for a
resource.
- After (!_zkClient.exists(zkPath)) check point, manually delete the
resource.
- New idealstate will be created using the update ideal state API.
### Expected behavior
- Update Ideal State API should not create new ideal state resource.
### Additional context
Add any other context about the problem here.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
