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

metrics: fix the residual label (#4824) #4828

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #4824

Signed-off-by: Ryan Leung [email protected]

What problem does this PR solve?

Issue Number: Close #4825.

What is changed and how it works?

Before collecting the metrics, reset the placementStatusGauge

Check List

Tests

  • Manual test (the detailed steps can be found in the above issue)

Release note

Fix the issue that the label distribution has residual labels

Signed-off-by: Ryan Leung <[email protected]>
@ti-chi-bot
Copy link
Member Author

ti-chi-bot commented Apr 21, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • disksing
  • nolouch

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/cherry-pick-not-approved type/cherry-pick-for-release-5.0 The PR belongs to release-5.0 cherry pick. labels Apr 21, 2022
@ti-chi-bot ti-chi-bot requested review from disksing and rleungx April 21, 2022 05:54
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Apr 24, 2022
@rleungx
Copy link
Member

rleungx commented May 27, 2022

/run-all-tests

@rleungx
Copy link
Member

rleungx commented May 30, 2022

/run-unit-tests

1 similar comment
@rleungx
Copy link
Member

rleungx commented May 30, 2022

/run-unit-tests

Signed-off-by: Ryan Leung <[email protected]>
@codecov
Copy link

codecov bot commented May 30, 2022

Codecov Report

Merging #4828 (ebaae6f) into release-5.0 (552c53e) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

@@               Coverage Diff               @@
##           release-5.0    #4828      +/-   ##
===============================================
- Coverage        74.98%   74.96%   -0.03%     
===============================================
  Files              245      245              
  Lines            24446    24447       +1     
===============================================
- Hits             18331    18326       -5     
- Misses            4500     4503       +3     
- Partials          1615     1618       +3     
Flag Coverage Δ
unittests 74.96% <100.00%> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
server/statistics/store_collection.go 95.20% <100.00%> (+0.03%) ⬆️
pkg/tempurl/tempurl.go 45.00% <0.00%> (-15.00%) ⬇️
server/id/id.go 76.19% <0.00%> (-4.77%) ⬇️
pkg/etcdutil/etcdutil.go 84.70% <0.00%> (-3.53%) ⬇️
client/base_client.go 82.98% <0.00%> (-1.55%) ⬇️
server/tso/global_allocator.go 71.01% <0.00%> (-1.45%) ⬇️
tools/pd-ctl/pdctl/command/operator.go 65.99% <0.00%> (-1.22%) ⬇️
pkg/btree/btree.go 85.30% <0.00%> (-0.97%) ⬇️
server/handler.go 41.97% <0.00%> (-0.50%) ⬇️
server/server.go 72.43% <0.00%> (-0.46%) ⬇️
... and 7 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 552c53e...ebaae6f. Read the comment docs.

@VelocityLight VelocityLight added cherry-pick-approved Cherry pick PR approved by release team. and removed do-not-merge/cherry-pick-not-approved labels Jun 13, 2022
@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Jun 13, 2022
@nolouch
Copy link
Contributor

nolouch commented Jun 13, 2022

/merge

@ti-chi-bot
Copy link
Member Author

@nolouch: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot
Copy link
Member Author

This pull request has been accepted and is ready to merge.

Commit hash: ebaae6f

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jun 13, 2022
@ti-chi-bot ti-chi-bot merged commit bcf3615 into tikv:release-5.0 Jun 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-approved Cherry pick PR approved by release team. release-note Denotes a PR that will be considered when it comes time to generate release notes. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/cherry-pick-for-release-5.0 The PR belongs to release-5.0 cherry pick.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants