ZhongJinHacker opened a new issue, #17232: URL: https://github.com/apache/dolphinscheduler/issues/17232
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened when we use K8S to deploy master nodes use scroll batch deploy mode, This situation has occurred with a certain probability that the master may gain the same slot id that lead some task would not be processed ### What you expected to happen I have read the log， and find the code location that can fix this issue, please assign this issue to me , I am glad to fix it ### How to reproduce use k8s to make master nodes pod down and make master nodes up when use k8s scroll deploy mode. ZooKeeper cannot ensure message ordering between different temporary znodes. And the field `masterServerMap` 's type is **ConcurrentHashMap** in Class `MasterClusters`. the value method of ConcurrentHashMap do not apply the ablity of ordering，so when the `getNormalServers`method in `MasterClusters` is called, it may return a list with different element order. It lead different master node may gain the same slot id .this situation will lead some task would not be processed forerver ### Anything else _No response_ ### Version dev ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
