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
Another issue is, that the client becomes unavailable while the PD leader is down and encounters the TsoBatchUsedUp since the writer needs to acquire TS from TSO in TiKV 6.2.0. While handing TsoBatchUsedUp, the region cache should not be clean since the region is unavailable right not doesn't means it's not a leader.
2. Minimal reproduce step (Required)
Create a 3-PD cluster and disable region cache every time after the request.
Kill the PD leader.
The client hangs.
3. What did you see instead (Required)
The client will recover after the PD leader is elected.
5. What are your Java Client and TiKV versions? (Required)
Client Java: master
TiKV: v6.2.0
The text was updated successfully, but these errors were encountered:
Bug Report
1. Describe the bug
While disabling the region cache and killing the PD leader, the client might be unavailable because of the wrong probe logic.
If the following code produces an exception like "retry is exhausted", the rest of the PD server will not be probed.
client-java/src/main/java/org/tikv/common/PDClient.java
Line 549 in 1b5edcd
Another issue is, that the client becomes unavailable while the PD leader is down and encounters the TsoBatchUsedUp since the writer needs to acquire TS from TSO in TiKV 6.2.0. While handing TsoBatchUsedUp, the region cache should not be clean since the region is unavailable right not doesn't means it's not a leader.
2. Minimal reproduce step (Required)
3. What did you see instead (Required)
5. What are your Java Client and TiKV versions? (Required)
The text was updated successfully, but these errors were encountered: