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

slack-19.0: various backports for vtorc, part 2 #596

Merged
merged 9 commits into from
Feb 5, 2025

Conversation

timvaillancourt
Copy link
Member

@timvaillancourt timvaillancourt commented Feb 4, 2025

Description

This PR contains backports of a collection of v20/v22 contributions to improve the visibility of the backend database, the topo-efficiency of discovery and the overall safety of VTOrc. Also, the upstream version of key-range support was backported, replacing the un-upstreamed support we added

Related Issue(s)

  1. Add api end point to print the current database state in VTOrc vitessio/vitess#15485 (v20 PR)
  2. Ensure all topo read calls consider --topo_read_concurrency vitessio/vitess#17276 (v22 PR)
  3. [release-19.0] vtorc: require topo for Healthy: true in /debug/health (#17129) vitessio/vitess#17351 (v19 backport of v22 PR)
  4. vtorc: fetch all tablets from cells once + filter during refresh vitessio/vitess#17388 (v22 PR)
  5. Support KeyRange in --clusters_to_watch flag vitessio/vitess#17604 (v22 PR)

This also included a revert of #457, to replace this code with the upstream variant: vitessio#17604

Checklist

  • "Backport to:" labels have been added if this change should be back-ported to release branches
  • If this change is to be back-ported to previous releases, a justification is included in the PR description
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on CI?
  • Documentation was added or is not required

Deployment Notes

@github-actions github-actions bot added this to the v19.0.7 milestone Feb 4, 2025
@timvaillancourt timvaillancourt changed the title slack-19.0: topo efficiency backports for vtorc, part 2 slack-19.0: v22 backports for vtorc, part 2 Feb 4, 2025
vitess-bot bot and others added 3 commits February 4, 2025 14:40
…ealth` (vitessio#17129) (vitessio#17351)

Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Manan Gupta <[email protected]>
Co-authored-by: vitess-bot[bot] <108069721+vitess-bot[bot]@users.noreply.github.com>
Co-authored-by: Tim Vaillancourt <[email protected]>
Co-authored-by: Manan Gupta <[email protected]>
Copy link

salesforce-cla bot commented Feb 4, 2025

Thanks for the contribution! Before we can merge this, we need @GuptaManan100 to sign the Salesforce Inc. Contributor License Agreement.

Signed-off-by: Tim Vaillancourt <[email protected]>
@timvaillancourt timvaillancourt marked this pull request as ready for review February 4, 2025 18:41
@timvaillancourt timvaillancourt requested a review from a team as a code owner February 4, 2025 18:41
@timvaillancourt timvaillancourt changed the title slack-19.0: v22 backports for vtorc, part 2 slack-19.0: various backports for vtorc, part 2 Feb 4, 2025
@timvaillancourt timvaillancourt merged commit a76e257 into slack-19.0 Feb 5, 2025
162 of 165 checks passed
@timvaillancourt timvaillancourt deleted the vtorc-topo-bps-pt2.slack-19.0 branch February 5, 2025 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants