Successive StoreNotMatch errors after add new store with tombstone store's IP

[lysu]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

0. start a region with 3 store(s1, s2, s3), and s1 is leader
1. make s1 as tombstone
2. add new s4 with s3's ip and make s4 as region leader
3. invoke query to hit region leader

2. What did you expect to see? (Required)

some storeNotMatch and recover quickly

3. What did you see instead (Required)

Successive StoreNotMatch errors after replace tombstone store with new store id and timeout for user query.

4. What is your TiDB version? (Required)

Release Version: None
Edition: Community
Git Commit Hash: None
Git Branch: None
UTC Build Time: None
GoVersion: go1.15
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false

[ti-srebot]

Please edit this comment or add a new comment to complete the following information

Not a bug

1. Remove the 'type/bug' label
2. Add notes to indicate why it is not a bug

Duplicate bug

1. Add the 'type/duplicate' label
2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

[v3.0.0:v3.0.20],[v4.0.0:v4.0.11],[v5.0.0-rc]

6. Fixed versions

master

[youjiali1995]

TiFlash meets the same problem. Close it.