bangbang2333 opened a new issue, #17439: URL: https://github.com/apache/dolphinscheduler/issues/17439
### 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 ### [Bug] [dolphinscheduler-registry-jdbc] Worker cannot recover after database outage in waiting strategy **What happened** 1. Configure DolphinScheduler in JDBC registry mode with the following parameters in `registry-disconnect-strategy`: ```yaml registry-disconnect-strategy: # The disconnect strategy: stop, waiting strategy: waiting max-waiting-time: 600s ``` 2. Start the worker normally; it connects to the registry successfully. 3. Simulate a database outage (disconnect the database). 4. Wait for some time, then restore the database. 5. Observe that the worker does not recover and goes into STOP state instead of resuming normal operation. ### What you expected to happen The worker should automatically reconnect to the registry and resume normal operation after the database is restored. ### How to reproduce ### [Bug] [dolphinscheduler-registry-jdbc] Worker cannot recover after database outage in waiting strategy **What happened** 1. Configure DolphinScheduler in JDBC registry mode with the following parameters in `registry-disconnect-strategy`: ```yaml registry-disconnect-strategy: # The disconnect strategy: stop, waiting strategy: waiting max-waiting-time: 600s ``` 2. Start the worker normally; it connects to the registry successfully. 3. Simulate a database outage (disconnect the database). 4. Wait for some time, then restore the database. 5. Observe that the worker does not recover and goes into STOP state instead of resuming normal operation. ### 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]
