[go: nahoru, domu]

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

High getregion operations may cause TiSpark job failed with EpochNotmach #2760

Open
King-Dylan opened this issue Aug 23, 2023 · 0 comments
Open

Comments

@King-Dylan
Copy link
King-Dylan commented Aug 23, 2023

Enhancement

For a cluster with huge number of regions, the getregion operation may cause the region cache to fail to be updated in time.Then Tispark may failed with EpochNotmach error when it need to acquire the new split region.
High getregion operations cause high pd cpu usage.
7e09efd5-93d0-4a7b-bf5a-f5106446f169
Then region heart can't be processed in time because of the high pd cpu usage and get region lock.If a region is split and merged at this time, an error may occur:"EpochNotMatch current epoch of region xxxxx is conf_ver: 362996 version: 168541, but you sent conf_ver: 362996 version: 168540"
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant