-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Add a system workflow to manage config #7570
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
base: main
Are you sure you want to change the base?
Conversation
| } | ||
|
|
||
| metadata.FailoverVersionIncrement = input.NewFVI | ||
| applied, err := a.clusterMetadataManager.SaveClusterMetadata(ctx, &persistence.SaveClusterMetadataRequest{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any potential race here (say cluster meta is changed by something else at the same time)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no. It is protected by the version.
|
This PR was marked as stale. Please update or close it. |
What changed?
Add a system workflwo to manage config
Why?
If the failover version never used, we can update the failover version increment. We should consider add a logic to check the namespace failover history.
How did you test it?
local test
Potential risks
Documentation
Is hotfix candidate?