mirror of
https://github.com/etcd-io/etcd.git
synced 2024-09-27 06:25:44 +00:00
7f46da223d
The existing client may connect to different endpoint from the specific endpoint to be maintained. Maintenance operations do not go through raft at all, so it might run into issue if the server hasn't finished applying the authentication request. Let's work with an example. Assuming the existing client connects to ep1, while the user wants to maintain ep2. If we getToken again, it sends an authentication request, which goes through raft. When the specific endpoint receives the maintenance request, it might haven't finished previous authentication request, but the new token is already carried in the context, so it will reject the maintenance request due to invalid token. We already have retry logic in `unaryClientInterceptor` and `streamClientInterceptor`. When the token expires, it can automatically refresh the token, so it should be safe to remove the `getToken` logic in `maintenance.dial` Signed-off-by: Benjamin Wang <wachao@vmware.com>