qiong-zhou opened a new issue, #17643: URL: https://github.com/apache/dolphinscheduler/issues/17643
### 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 In JdbcRegistry senario. When a master or worker client shutdown not by gracefully shutdown, the other client within the same registry will not discover this change even if this client is deleted after session timeout. ### What you expected to happen In JdbcRegistry senario. When a master or worker client shutdown, the other client will discover this change after session timeout. ### How to reproduce 1. My configuration `registry.type=jdbc` 2. Run 2 master clients. 3. Kill master `A` client with `kill -9 PID` 4. Wait until the session timeout. Master `B` will not update the master nodes and the command belong to master `A` will not be executed by master `B`. ### Anything else _No response_ ### Version 3.3.2 ### 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]
