High getregion operations may cause TiSpark job failed with EpochNotmach

[King-Dylan]

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.

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"