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

[release-19.0]: VTOrc optimize TMC usage (#15356) #15759

Merged
merged 1 commit into from
Apr 19, 2024

Conversation

GuptaManan100
Copy link
Member

Description

This is a backport of #15356

Related Issues

As described in #15726 (comment), this backport is required to fix the bug #15726.

@GuptaManan100 GuptaManan100 added Type: Feature Backport This is a backport Component: VTorc Vitess Orchestrator integration labels Apr 19, 2024
Copy link
Contributor

vitess-bot bot commented Apr 19, 2024

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.

@github-actions github-actions bot added this to the v19.0.4 milestone Apr 19, 2024
@GuptaManan100
Copy link
Member Author

I have verified manually, this change is fixing the memory leak in #15726

Copy link

codecov bot commented Apr 19, 2024

Codecov Report

Attention: Patch coverage is 1.75439% with 56 lines in your changes are missing coverage. Please review.

Project coverage is 67.43%. Comparing base (e60fbd7) to head (8ca5f00).

Files Patch % Lines
go/vt/vtorc/inst/instance_dao.go 0.00% 43 Missing ⚠️
go/vt/vtorc/logic/topology_recovery.go 16.66% 5 Missing ⚠️
go/vt/vtorc/inst/tablet_dao.go 0.00% 4 Missing ⚠️
go/vt/vtorc/logic/tablet_discovery.go 0.00% 3 Missing ⚠️
go/vt/vttablet/grpctmclient/client.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@              Coverage Diff              @@
##           release-19.0   #15759   +/-   ##
=============================================
  Coverage         67.43%   67.43%           
=============================================
  Files              1560     1560           
  Lines            192765   192760    -5     
=============================================
+ Hits             129991   129997    +6     
+ Misses            62774    62763   -11     

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

@deepthi
Copy link
Member

deepthi commented Apr 19, 2024

I'm curious about the codecov report. Looks like all this code is actually covered by e2e tests, but not unit tests?

@deepthi deepthi merged commit e167ca8 into vitessio:release-19.0 Apr 19, 2024
107 of 108 checks passed
@deepthi deepthi deleted the fix-vtorc-single-tmc branch April 19, 2024 05:27
@GuptaManan100
Copy link
Member Author

Yes exactly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backport This is a backport Component: VTorc Vitess Orchestrator integration Type: Bug Type: Feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants