You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2021/11/27 04:51:52 UTC
[GitHub] [dolphinscheduler] caishunfeng opened a new issue #7024: [Feature][MasterWorker] Self-recovery when master or worker lost connection from registry center
caishunfeng opened a new issue #7024:
URL: https://github.com/apache/dolphinscheduler/issues/7024
When master lost zk connection:
1. update current server state to `wait reconnect`
2. send server lost connection alert
3. keep quartz working (it will ensure work normally by quartz and db)
4. stop accepting new request
4. stop handling commands and process instances, clear the local running process instances; (it will be take over by other master)
5. wait to reconnect
6. when reconnect successfully, send server recover alert, update server state to `normal` and recover working
When worker lost zk connection:
1. update current server state to `wait reconnect`
2. send server lost connection alert
2. kill the running task (it will be task over by master and rerun)
3. stop accepting new request
4. wait to reconnect within a certain time
5. if reconnect timeout, stop itself
6. when reconnect successfully, send server recover alert, update server state to `normal` and recover working;
_Originally posted by @caishunfeng in https://github.com/apache/dolphinscheduler/discussions/6643#discussioncomment-1706255_
--
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
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #7024: [Feature][MasterWorker] Self-recovery when master or worker lost connection from registry center
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #7024:
URL: https://github.com/apache/dolphinscheduler/issues/7024#issuecomment-980502258
Hi:
* Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
* In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
* If you haven't received a reply for a long time, you can subscribe to the developer's email，Mail subscription steps reference https://dolphinscheduler.apache.org/en-us/community/development/subscribe.html ,Then write the issue URL in the email content and send question to dev@dolphinscheduler.apache.org.
--
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
[GitHub] [dolphinscheduler] github-actions[bot] closed issue #7024: [Feature][MasterWorker] Self-recovery when master or worker lost connection from registry center
Posted by GitBox <gi...@apache.org>.
github-actions[bot] closed issue #7024:
URL: https://github.com/apache/dolphinscheduler/issues/7024
--
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
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #7024: [Feature][MasterWorker] Self-recovery when master or worker lost connection from registry center
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #7024:
URL: https://github.com/apache/dolphinscheduler/issues/7024#issuecomment-1007034009
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
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #7024: [Feature][MasterWorker] Self-recovery when master or worker lost connection from registry center
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #7024:
URL: https://github.com/apache/dolphinscheduler/issues/7024#issuecomment-1013554709
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
[GitHub] [dolphinscheduler] shangeyao commented on issue #7024: [Feature][MasterWorker] Self-recovery when master or worker lost connection from registry center
Posted by GitBox <gi...@apache.org>.
shangeyao commented on issue #7024:
URL: https://github.com/apache/dolphinscheduler/issues/7024#issuecomment-987519026
please assign to me
--
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