weightedtarget: return a more meaningful error when no child policy is reporting READY #5391
Comments
|
@zasweq ping to assign this issue to me |
arvindbr8
added a commit
to arvindbr8/grpc-go
that referenced
this issue
Oct 12, 2022
…s reporting READY (grpc#5391)
arvindbr8
added a commit
to arvindbr8/grpc-go
that referenced
this issue
Oct 12, 2022
…s reporting READY (grpc#5391)
arvindbr8
added a commit
to arvindbr8/grpc-go
that referenced
this issue
Oct 12, 2022
…s reporting READY (grpc#5391)
arvindbr8
added a commit
to arvindbr8/grpc-go
that referenced
this issue
Oct 12, 2022
…s reporting READY (grpc#5391)
arvindbr8
added a commit
to arvindbr8/grpc-go
that referenced
this issue
Oct 12, 2022
…s reporting READY (grpc#5391)
arvindbr8
added a commit
to arvindbr8/grpc-go
that referenced
this issue
Oct 12, 2022
…s reporting READY (grpc#5391)
arvindbr8
added a commit
to arvindbr8/grpc-go
that referenced
this issue
Oct 13, 2022
…s reporting READY (grpc#5391)
arvindbr8
added a commit
to arvindbr8/grpc-go
that referenced
this issue
Oct 17, 2022
…s reporting READY (grpc#5391)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, if none of the children of the
weightedtargetLB policy are reportingREADY, the parent policy simply returns a picker which returns an error all the time with a message of "all subConns are in TransientFailure".grpc-go/balancer/weightedtarget/weightedaggregator/aggregator.go
Line 234 in 70a8055
This does not provide the user with any actionable information to fix the underlying problem. Surfacing the status message from the failing child pickers would give actionable information to the user to fix the underlying problem.
Java returns a weighted picker of all failing pickers in this scenario and C-core is planning to do the same. We should also do something similar.
The text was updated successfully, but these errors were encountered: