You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then send stale-read point-select SQL request to tidb0, then the stale-read get request in TiKV should be balanced in tikv0 and tikv1, and doesn't have stale-read get request in tikv2. But in TiDB v6.5.3, the stale-read request in tikv0 and tikv1 is unbalanced. Following is the TiKV metrics, as you can see, the stale-read get request on tikv0 is twice as high as on tikv1, which is not as expected, and there is no stale-read get request on tikv2, which is expected.
The text was updated successfully, but these errors were encountered:
TiDB Cluster Topology
Then send stale-read point-select SQL request to
tidb0
, then the stale-read get request in TiKV should be balanced intikv0
andtikv1
, and doesn't have stale-read get request intikv2
. But in TiDB v6.5.3, the stale-read request in tikv0 and tikv1 is unbalanced. Following is the TiKV metrics, as you can see, the stale-read get request on tikv0 is twice as high as on tikv1, which is not as expected, and there is no stale-read get request on tikv2, which is expected.The text was updated successfully, but these errors were encountered: