Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

client-go will not acquire new leader from other peer when enable grpc-forward #226

Open
Little-Wallace opened this issue Jul 12, 2021 · 0 comments
Assignees

Comments

@Little-Wallace
Copy link

In the method OnSendFail (see code in https://github.com/tikv/client-go/blob/master/internal/locate/region_cache.go#L842), client-go will try other peer when receive a rpc error from some store. But if user enables grpc-forward, client-go willl try forward this request to leader by other store. It means that if a TiKV node goes down, the client will keep trying to access the request on the dead node until the PD updates the region meta-information. But if the meta-informartion in PD does not update in time, the availability of TiKV cluster will decrease.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants