You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "bangbang2333 (via GitHub)" <gi...@apache.org> on 2025/08/22 06:05:16 UTC
[I] [Bug] [dolphinscheduler-registry-jdbc] Worker cannot recover after database outage in waiting strategy [dolphinscheduler]
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: commits-unsubscribe@dolphinscheduler.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] [dolphinscheduler-registry-jdbc] Worker cannot recover after database outage in waiting strategy [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #17439: [Bug] [dolphinscheduler-registry-jdbc] Worker cannot recover after database outage in waiting strategy
URL: https://github.com/apache/dolphinscheduler/issues/17439
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] [dolphinscheduler-registry-jdbc] Worker cannot recover after database outage in waiting strategy [dolphinscheduler]
Posted by "ruanwenjun (via GitHub)" <gi...@apache.org>.
ruanwenjun commented on issue #17439:
URL: https://github.com/apache/dolphinscheduler/issues/17439#issuecomment-3222426552
The waiting strategy has been removed at #https://github.com/apache/dolphinscheduler/pull/16821, seems some doc doesn't update.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] [dolphinscheduler-registry-jdbc] Worker cannot recover after database outage in waiting strategy [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #17439:
URL: https://github.com/apache/dolphinscheduler/issues/17439#issuecomment-3367645028
This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] [dolphinscheduler-registry-jdbc] Worker cannot recover after database outage in waiting strategy [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #17439:
URL: https://github.com/apache/dolphinscheduler/issues/17439#issuecomment-3336350977
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org