Client keeps updating the keyspace group discovery info #6508
Assignees
Labels
Comments
ti-chi-bot bot
added a commit
that referenced
this issue
May 25, 2023
…primary is changed (#6511) close #6508 Skip logging of the tso service discovery info when the secondar list is changed, because tso servers currently don't have consistent view of the member list due to remote etcd being used by tso service, which results in changing member list when the client queries the tso servers in round-robin. We need to improve the server side so that all tso servers can return the global consistent view of the keyspace groups' serving or membership info. Signed-off-by: Bin Shi <[email protected]> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
rleungx
pushed a commit
to rleungx/pd
that referenced
this issue
Aug 2, 2023
…primary is changed (tikv#6511) close tikv#6508 Skip logging of the tso service discovery info when the secondar list is changed, because tso servers currently don't have consistent view of the member list due to remote etcd being used by tso service, which results in changing member list when the client queries the tso servers in round-robin. We need to improve the server side so that all tso servers can return the global consistent view of the keyspace groups' serving or membership info. Signed-off-by: Bin Shi <[email protected]> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
What did you do?
What did you expect to see?
There should be a few logs about updating the info of the discovery.
What did you see instead?
Too frequently and the members field keeps changing.
What version of PD are you using (
pd-server -V)?master
The text was updated successfully, but these errors were encountered: