AccessFollower will try to access unreachable leader peers #46198
Labels
affects-6.5
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-7.1
severity/major
sig/transaction
SIG:Transaction
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Run a stale read workload and inject network partition between two zones.
2. What did you expect to see? (Required)
KV client should never try to access unreachable peers.
3. What did you see instead (Required)
accessFollower
may choose an unreachable leader peer as the target after fallback from data-not-ready error, which leads to unexpected long-tail queries.4. What is your TiDB version? (Required)
release-6.5
The text was updated successfully, but these errors were encountered: