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

Change healthcheck to only reload specific keyspace shard tablets #17872

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

GuptaManan100
Copy link
Member

@GuptaManan100 GuptaManan100 commented Feb 26, 2025

Description

This PR fixes the issue described in #17876. As the issue points out, we should only be loading tablets for the specific keyspace-shard that we don't have a primary for anymore.

This PR makes this change, by changing the load tablets trigger, to also store the keyspace shard information, and we use that to only load some of the tablets.

As part of this change, I also found that as part of the PR #17071 we introduced a couple of fields to hte GetTabletsByCellOptions but they weren't being respected in the GetTabletsMap function. This PR fixes this too, and adds tests for all the topo functions touched. The implementation of a couple of them has also been changed to improve efficiency.

Related Issue(s)

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

Copy link
Contributor

vitess-bot bot commented Feb 26, 2025

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot added NeedsBackportReason If backport labels have been applied to a PR, a justification is required NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsIssue A linked issue is missing for this Pull Request NeedsWebsiteDocsUpdate What it says labels Feb 26, 2025
@github-actions github-actions bot added this to the v22.0.0 milestone Feb 26, 2025
Copy link

codecov bot commented Feb 27, 2025

Codecov Report

Attention: Patch coverage is 89.00000% with 11 lines in your changes missing coverage. Please review.

Project coverage is 67.53%. Comparing base (b05df12) to head (36bc2b6).
Report is 7 commits behind head on main.

Files with missing lines Patch % Lines
go/vt/topo/tablet.go 88.88% 6 Missing ⚠️
go/vt/discovery/topology_watcher.go 86.66% 4 Missing ⚠️
go/vt/topo/shard.go 88.88% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main   #17872      +/-   ##
==========================================
+ Coverage   67.45%   67.53%   +0.07%     
==========================================
  Files        1594     1595       +1     
  Lines      259064   259701     +637     
==========================================
+ Hits       174760   175377     +617     
- Misses      84304    84324      +20     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@GuptaManan100 GuptaManan100 added Type: Bug Component: Cluster management Type: Enhancement Logical improvement (somewhere between a bug and feature) and removed NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says NeedsIssue A linked issue is missing for this Pull Request NeedsBackportReason If backport labels have been applied to a PR, a justification is required labels Feb 28, 2025
@GuptaManan100 GuptaManan100 marked this pull request as ready for review February 28, 2025 05:03
Comment on lines +649 to +653
// if we get a partial result, we keep going. It most likely means
// a cell is out of commission.
aliases, err := ts.FindAllTabletAliasesInShardByCell(ctx, keyspace, shard, cells)
if err != nil && !IsErrType(err, PartialResult) {
return nil, err
Copy link
Member

Choose a reason for hiding this comment

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

The changes to this func make it correct, but slower. Previously the keyspace and shard were being ignored and we'd return all tablets. Where is this func being used, and what is the impact of fetching each tablet from topo versus (in the best case) a single topo call fetching all tablets?

Copy link
Member Author

Choose a reason for hiding this comment

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

It is being used only in VTOrc to refresh the tablets in a specific keyspace shard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Cluster management Type: Bug Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug Report: Wasteful Topo calls in loadTabletsTrigger in the healthcheck
2 participants