Skip to content
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

Add tolerable replication lag value #511

Merged
merged 2 commits into from
Dec 12, 2023
Merged

Add tolerable replication lag value #511

merged 2 commits into from
Dec 12, 2023

Conversation

GuptaManan100
Copy link
Collaborator

@GuptaManan100 GuptaManan100 commented Dec 11, 2023

Description

In the operator, we are calling PlannedReparentShard from the wrangler and an argument to that was recently added to it that specifies the amount of replication lag considered to be tolerable when initiating a PRS.

The vitess change was made in the PR vitessio/vitess#14634

Signed-off-by: Manan Gupta <[email protected]>
Copy link
Collaborator

@deepthi deepthi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this made a Keyspace/Shard property in the operator so that people can override it?
Or is that a bad idea?

@GuptaManan100
Copy link
Collaborator Author

Vitess operator only issues PlannedReparentShard when it needs to drain a tablet. The timeout for that PRS is not yet configurable, so I think it is okay to have a hard-coded value for now. If we feel the need to make them configurable, we can add them as a follow-up.

@frouioui frouioui merged commit cac207f into main Dec 12, 2023
9 checks passed
@frouioui frouioui deleted the fix-prs-lag branch December 12, 2023 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants