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

server: partially fix grpc status #4798

Merged
merged 3 commits into from
Apr 9, 2022
Merged

server: partially fix grpc status #4798

merged 3 commits into from
Apr 9, 2022

Conversation

rleungx
Copy link
Member

@rleungx rleungx commented Apr 8, 2022

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

What problem does this PR solve?

Issue Number: Ref #4797.

What is changed and how it works?

This PR removes unnecessary withStack and partially fix the above issue.

Check List

Tests

  • Unit test

Release note

Fix the issue that the status code of `not leader` is sometimes wrong 

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

ti-chi-bot commented Apr 8, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • JmPotato
  • 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 the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Apr 8, 2022
@codecov
Copy link

codecov bot commented Apr 8, 2022

Codecov Report

Merging #4798 (6ef6169) into master (bd1a18b) will decrease coverage by 0.01%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##           master    #4798      +/-   ##
==========================================
- Coverage   75.24%   75.22%   -0.02%     
==========================================
  Files         294      294              
  Lines       28509    28509              
==========================================
- Hits        21452    21447       -5     
- Misses       5151     5156       +5     
  Partials     1906     1906              
Flag Coverage Δ
unittests 75.22% <25.00%> (-0.02%) ⬇️

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

Impacted Files Coverage Δ
server/grpc_service.go 54.61% <25.00%> (+0.45%) ⬆️
pkg/metricutil/metricutil.go 82.75% <0.00%> (-10.35%) ⬇️
server/schedulers/shuffle_hot_region.go 55.55% <0.00%> (-10.11%) ⬇️
server/schedule/region_scatterer.go 78.99% <0.00%> (-4.21%) ⬇️
server/election/leadership.go 73.19% <0.00%> (-2.07%) ⬇️
server/statistics/store_collection.go 93.66% <0.00%> (-1.41%) ⬇️
pkg/btree/btree.go 87.37% <0.00%> (-0.76%) ⬇️
server/cluster/coordinator.go 75.11% <0.00%> (-0.24%) ⬇️
client/client.go 70.10% <0.00%> (-0.11%) ⬇️
server/member/member.go 63.68% <0.00%> (ø)
... and 10 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 bd1a18b...6ef6169. Read the comment docs.

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

@AndreMouche AndreMouche 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
Copy link
Member

@AndreMouche: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments.

In response to this:

LGTM

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 added the status/LGT1 Indicates that a PR has LGTM 1. label Apr 8, 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 Apr 9, 2022
@JmPotato
Copy link
Member

JmPotato commented Apr 9, 2022

/merge

@ti-chi-bot
Copy link
Member

@JmPotato: 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: 258b74b

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Apr 9, 2022
@ti-chi-bot ti-chi-bot merged commit e3fd147 into tikv:master Apr 9, 2022
@rleungx rleungx deleted the status-1 branch April 11, 2022 04:00
@rleungx rleungx 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. labels Jun 22, 2022
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this pull request Jun 22, 2022
@ti-chi-bot
Copy link
Member

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

ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this pull request Jun 22, 2022
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this pull request Jun 22, 2022
@ti-chi-bot
Copy link
Member

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

@ti-chi-bot
Copy link
Member

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

ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this pull request Jun 22, 2022
@ti-chi-bot
Copy link
Member

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

ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this pull request Jun 22, 2022
@ti-chi-bot
Copy link
Member

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

ti-chi-bot added a commit that referenced this pull request Jun 23, 2022
ref #4797, ref #4798

Signed-off-by: ti-chi-bot <[email protected]>
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 Jul 5, 2022
ref #4797, ref #4798

Signed-off-by: ti-chi-bot <[email protected]>
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 Jul 5, 2022
ref #4797, ref #4798

Signed-off-by: ti-chi-bot <[email protected]>
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 Jul 18, 2022
ref #4797, ref #4798

Signed-off-by: ti-chi-bot <[email protected]>
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 Sep 21, 2022
ref #4797, ref #4798

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

Co-authored-by: Ryan Leung <[email protected]>
@rleungx rleungx mentioned this pull request Aug 29, 2023
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. 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.

5 participants