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

Drop store cache and region cache when handling StoreNotMatch region error #21584

Closed
disksing opened this issue Dec 9, 2020 · 2 comments
Closed
Assignees
Labels
component/tikv duplicate Issues or pull requests already exists. severity/major type/bug The issue is confirmed as a bug.

Comments

@disksing
Copy link
Contributor

disksing commented Dec 9, 2020

Bug Report

1. Minimal reproduce step (Required)

  1. Start a cluster. Prepare some data.
  2. Run some query to fill TiDB's region cache.
  3. Delete a TiKV (Offline -> Tombstone)
  4. Add the TiKV node (same address, same port) to another cluster.
  5. Send some query to the old TiDB server again.

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

  • TiDB will get 'StoreNotMatch' from TiKV server.
  • TiDB drops StoreInfo and RegionInfo that are out of date.
  • TiDB reloads metas from PD.
  • The 'StoreNotMatch' errors disappear.

3. What did you see instead (Required)

  • TiDB gets 'StoreNotMatch` error.
  • TiDB keeps reporting 'StoreNotMatch' error.

4. What is your TiDB version? (Required)

v3.0.5

@disksing disksing added the type/bug The issue is confirmed as a bug. label Dec 9, 2020
@XuHuaiyu XuHuaiyu added component/tikv and removed sig/execution SIG execution labels Dec 14, 2020
@youjiali1995 youjiali1995 self-assigned this Jan 22, 2021
@youjiali1995
Copy link
Contributor

#11567 should fix it. When meets StoreNotMatch and the old store is a tombstone, TiDB will invalidate the store and all regions on it.

@ti-srebot
Copy link
Contributor

ti-srebot commented Jan 26, 2021

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

Duplicate bug

Already fixed by #11567

@youjiali1995 youjiali1995 added the duplicate Issues or pull requests already exists. label Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/tikv duplicate Issues or pull requests already exists. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

5 participants