-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Improvement][master] Optimize failover #9263
Labels
feature
new feature
Comments
Hi:
|
huagetai
added a commit
to huagetai/dolphinscheduler
that referenced
this issue
Mar 30, 2022
- add FailoverService.java - move failover method from MasterRegistryClient to FailoverService - move failover code from FailoverExecuteThread to FailoverService This closes apache#9263
caishunfeng
pushed a commit
that referenced
this issue
Apr 12, 2022
- add FailoverService.java - move failover method from MasterRegistryClient to FailoverService - move failover code from FailoverExecuteThread to FailoverService This closes #9263
Tianqi-Dotes
pushed a commit
to Tianqi-Dotes/dolphinscheduler
that referenced
this issue
Jun 16, 2022
- add FailoverService.java - move failover method from MasterRegistryClient to FailoverService - move failover code from FailoverExecuteThread to FailoverService This closes apache#9263
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
Description
Now Master server failover is mainly implemented by MasterRegistryClient and FailoverExecuteThread。Consider whether the failover code can be isolated。
This makes the responsibilities clearer:
MasterRegistryClient--Responsible for node registration、state listener、 removing dead server
FailoverExecuteThread--Responsible for executing failover
FailoverService--Responsible for failover
Use case
The function of the refactored class is clearer
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: