I am using Java gRPC version 1.24.1. When debugging some timed out requests
I found out that sometimes client calls all hedging requests ( 3 in my
case) on the same server endpoint.
NameResolver.Listener.onAddresses() got updated with 3 distinct endpoints
before first call was made.
Is it a bug in gRPC code ? Even if 2 out of 3 servers were unreachable,
having all hedging attempts go to a single endpoint is not the best option.
status-code=DEADLINE_EXCEEDED status-description=deadline exceeded after
9999958644ns. [closed=[], open=[[remote_addr=xxx.com/xxx.xxx.xxx.xxx:3112],
[remote_addr=xxx.com/xxx.xxx.xxx.xxx:3112], [remote_addr=xxx.com/xxx.xxx.xxx
.xxx:3112]]]
Thanks,
David
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/d2413543-92b1-42a9-9642-7c67bd255f53%40googlegroups.com.
