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

store/tikv: limit batch split count for one request #18191

Merged
merged 4 commits into from
Jul 21, 2020

Conversation

Connor1996
Copy link
Member

@Connor1996 Connor1996 commented Jun 23, 2020

Signed-off-by: Connor1996 [email protected]

What problem does this PR solve?

Too much split may cause TiKV latency spike.

What is changed and how it works?

For one batch split request, TiKV will write all newly created regions' metadata into one write batch of RocksDB. So limit the batch split for one request and separate it into multiple requests.

Related changes

  • Need to cherry-pick to the release branch

Check List

  • Manual test (add detailed scripts or steps below)

Release note

  • Limit batch split count for one request

@Connor1996
Copy link
Member Author

/release

@Connor1996
Copy link
Member Author

PTAL @crazycs520 @zhangjinpeng1987

@Connor1996
Copy link
Member Author

/release

Copy link
Contributor

@crazycs520 crazycs520 left a comment

Choose a reason for hiding this comment

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

LGTM

@codecov
Copy link

codecov bot commented Jun 23, 2020

Codecov Report

Merging #18191 into master will increase coverage by 0.8742%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             master     #18191        +/-   ##
================================================
+ Coverage   79.5137%   80.3879%   +0.8742%     
================================================
  Files           535        535                
  Lines        144111     149546      +5435     
================================================
+ Hits         114588     120217      +5629     
+ Misses        20274      20094       -180     
+ Partials       9249       9235        -14     

@crazycs520 crazycs520 added needs-cherry-pick-3.0 type/enhancement The issue or PR belongs to an enhancement. labels Jun 23, 2020
@crazycs520
Copy link
Contributor

/release

@crazycs520
Copy link
Contributor

/build

Copy link
Contributor

@zimulala zimulala left a comment

Choose a reason for hiding this comment

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

LGTM

@zimulala zimulala added the status/can-merge Indicates a PR has been approved by a committer. label Jun 24, 2020
@ti-srebot
Copy link
Contributor

/run-all-tests

@ti-srebot
Copy link
Contributor

/run-all-tests

@zz-jason
Copy link
Member

/merge

@ti-srebot
Copy link
Contributor

@zz-jason Oops! This PR requires at least 2 LGTMs to merge. The current number of LGTM is 0.

@zz-jason
Copy link
Member

/merge

@ti-srebot
Copy link
Contributor

@zz-jason Oops! This PR requires at least 2 LGTMs to merge. The current number of LGTM is 0.

@zz-jason
Copy link
Member

/approve

@ti-srebot ti-srebot added the status/LGT1 Indicates that a PR has LGTM 1. label Jul 21, 2020
@zz-jason zz-jason merged commit 49406ac into pingcap:master Jul 21, 2020
ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Jul 21, 2020
@ti-srebot
Copy link
Contributor

cherry pick to release-3.0 in PR #18694

ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Jul 21, 2020
@ti-srebot
Copy link
Contributor

cherry pick to release-3.1 in PR #18695

ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Jul 21, 2020
@ti-srebot
Copy link
Contributor

cherry pick to release-4.0 in PR #18696

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants