We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The client can't get the real caused of error.
Server side:
Aug 22, 2024 @ 11:08:57.788 | {"level":"warn","time":"2024-08-22T11:08:57.788091476Z","component":"leader-controller","error":{"error":"rpc error: code = Code(104) desc = oxia: node is shutting down","kind":"*status.Error","stack":null},"namespace":"xxx","peer":"192.168.2.249:58692","shard":1,"term":16,"time":"2024-08-22T11:08:57.788102614Z","message":"Failed to dispatch notifications"}
Java Client side:
2024-08-22T11:08:57,805+0000 [grpc-default-worker-ELG-2-3] WARN io.streamnative.oxia.client.notify.ShardNotificationReceiver - Error while receiving notifications for shard=1: CANCELLED: context canceled - Retrying in 0.113 seconds
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Motivation
The client can't get the real caused of error.
Server side:
Java Client side:
The text was updated successfully, but these errors were encountered: