junkaixue commented on issue #2793: URL: https://github.com/apache/helix/issues/2793#issuecomment-2166497363
Interesting. I cannot reproduce it in my local. One possible situation could be you add/delete the same resource very close and almost same time. But the controller is busy with handling other notification. Helix use selective update for the metadata: 1. The delete will trigger a child change for ZK. 2. The add will trigger another child change. 3. But if these two operations are close. Then controller will see the child change event and when read data from ZK, the IS already added back. So controller thinks there is no change. Even your number of partition has been changed, from ZK PoV, it is not data change and will not trigger refresh of data. In this case, either you can create the resource with different name like add some version to differentiate resource. Or add logic to make sure participants start dropping partitions then create the new ones with same name. -- 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]
