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

placement: change ValidateStores condition #4700

Merged
merged 4 commits into from
Mar 4, 2022

Conversation

CabinfeverB
Copy link
Member

Signed-off-by: Cabinfever_B [email protected]

What problem does this PR solve?

Issue Number: Close #4690

What is changed and how it works?

change and to or

change ValidateStores condition

Check List

Tests

  • Unit test

Release note

 None.

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

ti-chi-bot commented Mar 3, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • lhy1024
  • rleungx

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-none Denotes a PR that doesn't merit a release note. label Mar 3, 2022
@ti-chi-bot ti-chi-bot requested review from lhy1024 and Yisaer March 3, 2022 06:32
Signed-off-by: Cabinfever_B <[email protected]>
Signed-off-by: Cabinfever_B <[email protected]>
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Mar 3, 2022
@codecov
Copy link

codecov bot commented Mar 3, 2022

Codecov Report

Merging #4700 (3285b6b) into master (e25d403) will increase coverage by 0.02%.
The diff coverage is 85.71%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4700      +/-   ##
==========================================
+ Coverage   75.05%   75.08%   +0.02%     
==========================================
  Files         283      283              
  Lines       27842    27849       +7     
==========================================
+ Hits        20898    20910      +12     
+ Misses       5080     5076       -4     
+ Partials     1864     1863       -1     
Flag Coverage Δ
unittests 75.08% <85.71%> (+0.02%) ⬆️

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

Impacted Files Coverage Δ
client/client.go 68.89% <0.00%> (+0.10%) ⬆️
server/cluster/prepare_checker.go 90.00% <0.00%> (ø)
server/handler.go 51.22% <0.00%> (-0.41%) ⬇️
server/schedulers/evict_slow_store.go 53.33% <33.33%> (ø)
server/cluster/unsafe_recovery_controller.go 79.86% <50.00%> (ø)
server/schedule/checker/rule_checker.go 78.97% <50.00%> (ø)
pkg/autoscaling/calculation.go 58.41% <100.00%> (ø)
server/api/store.go 65.24% <100.00%> (ø)
server/cluster/cluster.go 84.91% <100.00%> (ø)
server/core/store.go 81.34% <100.00%> (+0.14%) ⬆️
... and 33 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 6b0cafb...3285b6b. Read the comment docs.

Copy link
Contributor

@lhy1024 lhy1024 left a comment

Choose a reason for hiding this comment

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

Do we need to add a test to avoid similar code?

@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 Mar 3, 2022
@CabinfeverB
Copy link
Member Author

Do we need to add a test to avoid similar code?

I don't think it's easy to avoid similar code with additional tests. It's good behavior that when creating stores, try to add heartbeat information

@rleungx
Copy link
Member

rleungx commented Mar 4, 2022

/merge

@ti-chi-bot
Copy link
Member

@rleungx: 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: 32023ef

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Mar 4, 2022
@ti-chi-bot ti-chi-bot merged commit bf2d784 into tikv:master Mar 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note-none Denotes a PR that doesn't merit a release note. 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.

Flawed judgment conditions when validating stores in rule checker
5 participants