We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1、update the config of tso
the primary changed once when tso rolling update
the primary changed twice when tso rolling update
pd-server -V
./pd-server -V Release Version: v8.0.0-alpha Edition: Community Git Commit Hash: bc92c13 Git Branch: heads/refs/tags/v8.0.0-alpha UTC Build Time: 2024-03-27 11:37:04 2024-03-28T15:26:29.929+0800
The text was updated successfully, but these errors were encountered:
/type bug /severity major /assign HuSharp
Sorry, something went wrong.
We can upgrade pdms primary in last place(named defer feature) can avoid unnecessary primary transfer
Ref pingcap/tiup#2414
tidb-operator does not have the ability to defer feature, it can only upgrade the pods in order.
defer feature
Furthermore, Thinking about this situation:
To fix it, Assume that current primary ordinal is x, and range is [0, n]
Ref pingcap/tidb-operator#5643
HuSharp
Successfully merging a pull request may close this issue.
Bug Report
What did you do?
1、update the config of tso
What did you expect to see?
the primary changed once when tso rolling update
What did you see instead?
the primary changed twice when tso rolling update
What version of PD are you using (
pd-server -V
)?./pd-server -V
Release Version: v8.0.0-alpha
Edition: Community
Git Commit Hash: bc92c13
Git Branch: heads/refs/tags/v8.0.0-alpha
UTC Build Time: 2024-03-27 11:37:04
2024-03-28T15:26:29.929+0800
The text was updated successfully, but these errors were encountered: