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

Merged
merged 1 commit into from
Apr 21, 2022

Conversation

rleungx
Copy link
Member

@rleungx rleungx commented Apr 20, 2022

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

ti-chi-bot commented Apr 20, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • CabinfeverB
  • lhy1024

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 do-not-merge/needs-linked-issue do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Apr 20, 2022
@ti-chi-bot ti-chi-bot requested review from disksing and nolouch April 20, 2022 06:41
@codecov
Copy link

codecov bot commented Apr 20, 2022

Codecov Report

Merging #4824 (378d9c4) into master (783d060) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #4824   +/-   ##
=======================================
  Coverage   75.35%   75.35%           
=======================================
  Files         295      295           
  Lines       28809    28810    +1     
=======================================
+ Hits        21709    21710    +1     
+ Misses       5182     5181    -1     
- Partials     1918     1919    +1     
Flag Coverage Δ
unittests 75.35% <100.00%> (+<0.01%) ⬆️

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

Impacted Files Coverage Δ
server/statistics/store_collection.go 95.10% <100.00%> (+0.03%) ⬆️
pkg/tempurl/tempurl.go 45.00% <0.00%> (-15.00%) ⬇️
server/tso/local_allocator.go 71.62% <0.00%> (-6.76%) ⬇️
server/id/id.go 76.19% <0.00%> (-4.77%) ⬇️
server/tso/tso.go 61.71% <0.00%> (-4.01%) ⬇️
server/server.go 74.21% <0.00%> (-1.72%) ⬇️
server/cluster/cluster.go 85.90% <0.00%> (-0.35%) ⬇️
server/grpc_service.go 53.87% <0.00%> (-0.18%) ⬇️
client/client.go 69.03% <0.00%> (-0.11%) ⬇️
server/handler.go 53.21% <0.00%> (+0.38%) ⬆️
... 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 783d060...378d9c4. Read the comment docs.

@rleungx rleungx marked this pull request as ready for review April 20, 2022 06:52
@ti-chi-bot ti-chi-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 20, 2022
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Apr 20, 2022
Copy link
Member

@CabinfeverB CabinfeverB left a comment

Choose a reason for hiding this comment

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

LGTM

@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 Apr 20, 2022
@nolouch nolouch added needs-cherry-pick-release-5.0 The PR needs to cherry pick to release-5.0 branch. needs-cherry-pick-release-5.1 Type: Need cherry pick to release-5.1 needs-cherry-pick-release-5.2 Type: Need cherry pick to release-5.2 needs-cherry-pick-release-5.3 Type: Need cherry pick to release-5.3 needs-cherry-pick-release-5.4 Should cherry pick this PR to release-5.4 branch. needs-cherry-pick-release-6.0 The PR needs to cherry pick to release-6.0 branch. labels Apr 21, 2022
@nolouch nolouch added needs-cherry-pick-release-5.4 Should cherry pick this PR to release-5.4 branch. needs-cherry-pick-release-6.0 The PR needs to cherry pick to release-6.0 branch. labels Apr 21, 2022
@nolouch
Copy link
Contributor

nolouch commented Apr 21, 2022

/merge

1 similar comment
@nolouch
Copy link
Contributor

nolouch commented Apr 21, 2022

/merge

@ti-chi-bot
Copy link
Member

@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.

1 similar comment
@ti-chi-bot
Copy link
Member

@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

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

Commit hash: 378d9c4

1 similar comment
@ti-chi-bot
Copy link
Member

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

Commit hash: 378d9c4

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Apr 21, 2022
@nolouch
Copy link
Contributor

nolouch commented Apr 21, 2022

/merge

@ti-chi-bot
Copy link
Member

@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 ti-chi-bot merged commit 6c5d61c into tikv:master Apr 21, 2022
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #4826.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #4827.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #4828.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #4829.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #4830.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #4831.

ti-chi-bot added a commit that referenced this pull request Apr 26, 2022
ref #4824, close #4825

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

Co-authored-by: Ryan Leung <[email protected]>
ti-chi-bot added a commit that referenced this pull request May 27, 2022
ref #4824, close #4825

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

Co-authored-by: Ryan Leung <[email protected]>
ti-chi-bot added a commit that referenced this pull request May 27, 2022
ref #4824, close #4825

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

Co-authored-by: Ryan Leung <[email protected]>
ti-chi-bot added a commit that referenced this pull request Jun 13, 2022
ref #4824, close #4825

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

Co-authored-by: Ryan Leung <[email protected]>
ti-chi-bot added a commit that referenced this pull request Jun 13, 2022
ref #4824, close #4825

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

Co-authored-by: Ryan Leung <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-cherry-pick-release-5.0 The PR needs to cherry pick to release-5.0 branch. needs-cherry-pick-release-5.1 Type: Need cherry pick to release-5.1 needs-cherry-pick-release-5.2 Type: Need cherry pick to release-5.2 needs-cherry-pick-release-5.3 Type: Need cherry pick to release-5.3 needs-cherry-pick-release-5.4 Should cherry pick this PR to release-5.4 branch. needs-cherry-pick-release-6.0 The PR needs to cherry pick to release-6.0 branch. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Label distribution has residual labels
6 participants