Skip to content

retry: Status should indicate more details when retries are enabled and an RPC fails #7023

@ukai

Description

@ukai

NOTE: if you are reporting is a potential security vulnerability or a crash,
please follow our CVE process at
https://github.com/grpc/proposal/blob/master/P4-grpc-cve-process.md instead of
filing an issue here.

Please see the FAQ in our main README.md, then answer the questions below
before submitting your issue.

What version of gRPC are you using?

v1.61.0

What version of Go are you using (go version)?

go 1.21.7

What operating system (Linux, Windows, …) and version?

Linux

What did you do?

If possible, provide a recipe for reproducing the error.

We set service config like this
https://chromium.googlesource.com/infra/infra/+/86b0e81fba4005098b1bec9ca40018fc3dacd523/go/src/infra/build/siso/reapi/reapi.go#99
with https://github.com/bazelbuild/remote-apis-sdks/tree/master/go/pkg/balancer

What did you expect to see?

We expect grpc retries for unavailable error.

What did you see instead?

Seems not retries for error

rpc error: code = Unavailable desc = error reading from server: read tcp 10.0.11.175:47388->64.233.183.95:443: read: connection reset by peer

https://ci.chromium.org/ui/p/chromium/builders/build/build-perf-android-siso/1597/overview

Metadata

Metadata

Assignees

Labels

Area: ClientIncludes Channel/Subchannel/Streams, Connectivity States, RPC Retries, Dial/Call Options and more.P2Type: FeatureNew features or improvements in behavior

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions