Round-robin updateMember may cause the timestamp to fallback #6770
Labels
affects-7.6
affects-8.1
component/client
Client logic.
component/keyspace
Key space.
component/tso
Timestamp Oracle.
may-affects-5.4
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
We use a round-robin way to request the TSO server with
FindGroupByKeyspaceID
gRPC call.pd/client/tso_service_discovery.go
Lines 418 to 441 in b176a0a
However, if the requested TSO server satisfies this kind of case, it may cause the timestamp to fallback.
If we do
updateMember
quickly while requesting the TSO, it may cause the keyspace group in the request to change between the default group and group 1, resulting in the timestamp fallback.The text was updated successfully, but these errors were encountered: