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/copr: invalidate stale regions for Mpp query. #24410

Merged

Conversation

hanfei1991
Copy link
Member

@hanfei1991 hanfei1991 commented May 3, 2021

What problem does this PR solve?

relate issue: pingcap/tiflash#1873

Problem Summary:
Right now, we won't update the stale regions during executing Mpp queries. Then we added the try regions field in MppDispatchTask reponse. In this pr, we try to invalidate the stale regions in the mppr response.

What is changed and how it works?

Related changes

pingcap/kvproto#751

Check List

Tests

  • Manual test (add detailed scripts or steps below)
    • Insert data continously
    • observe that tiflash is retrying regions. In my case, the log is like ["DAGQueryBlockInterpreter: Start to retry 1 regions (10936,)"]
    • observe log in tidb, find ["invalid region because tiflash detected stale region"] ["region id"="{ region id: 10936, ver: 116, confVer: 2 }"] proving this function works.

Release note

  • store/copr: invalidate stale regions for Mpp query.

@ti-chi-bot ti-chi-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label May 3, 2021
@purelind
Copy link
Contributor

purelind commented May 3, 2021

/run-check-title

1 similar comment
@purelind
Copy link
Contributor

purelind commented May 3, 2021

/run-check-title

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label May 6, 2021
@fzhedu
Copy link
Contributor

fzhedu commented May 6, 2021

/LGTM

@ti-chi-bot
Copy link
Member

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • fzhedu
  • qw4990

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

@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 May 6, 2021
@fzhedu
Copy link
Contributor

fzhedu commented May 6, 2021

/merge

@ti-chi-bot
Copy link
Member

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

Commit hash: 8ec6481

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label May 6, 2021
@ti-chi-bot ti-chi-bot merged commit c269b11 into pingcap:master May 6, 2021
ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request May 6, 2021
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.0 in PR #24432

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 size/M Denotes a PR that changes 30-99 lines, ignoring generated files. 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.

6 participants