Skip to content

invalidate stale regions for Mpp query. (#1859)#1877

Merged
ti-srebot merged 6 commits intopingcap:release-5.0from
ti-srebot:release-5.0-2956eafe6aae
Jun 18, 2021
Merged

invalidate stale regions for Mpp query. (#1859)#1877
ti-srebot merged 6 commits intopingcap:release-5.0from
ti-srebot:release-5.0-2956eafe6aae

Conversation

@ti-srebot
Copy link
Collaborator

@ti-srebot ti-srebot commented May 8, 2021

cherry-pick #1859 to release-5.0
You can switch your code base to this Pull Request by using git-extras:

# In tics repo:
git pr https://github.com/pingcap/tics/pull/1877

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tics.git pr/1877:release-5.0-2956eafe6aae

What problem does this PR solve?

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 and try to invalidate the stale regions on TiDB side.

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

  • invalidate stale regions for Mpp query.

Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot ti-srebot added CHERRY-PICK cherry pick status/LGT1 Indicates that a PR has LGTM 1. labels May 8, 2021
@ti-srebot ti-srebot added this to the v5.0.2 milestone May 8, 2021
@windtalker
Copy link
Contributor

Should use the release-5.0 branch of kvproto

@JaySon-Huang JaySon-Huang modified the milestones: v5.0.2, v5.0.3 Jun 3, 2021
@hanfei1991
Copy link
Member

/merge

@ti-srebot
Copy link
Collaborator Author

@hanfei1991 Oops! This PR requires at least 1 LGTMs to merge. The current number of LGTM is 0

Copy link
Contributor

@windtalker windtalker left a comment

Choose a reason for hiding this comment

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

LGTM

@hanfei1991
Copy link
Member

/merge

@ti-srebot
Copy link
Collaborator Author

Your auto merge job has been accepted, waiting for:

  • 2085

@ti-srebot ti-srebot added the status/can-merge Indicates a PR has been approved by a committer. label Jun 18, 2021
@ti-srebot
Copy link
Collaborator Author

/run-all-tests

@ti-srebot ti-srebot merged commit f46a27e into pingcap:release-5.0 Jun 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CHERRY-PICK cherry pick status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants