Sam Batschelet
Sam Batschelet
cc @LucioFranco it appears that you reviewed the original PR. Thanks in advance.
@zasweq curious if we think it could be related to this bug in net/http2[1]? Could you help drive priority? This is causing huge problems for us in production with golang...
cc @dfawley please reopen?
> Hi, > > Really sorry to resurrect this thread again but the issue still seems to persist. That is to say, following the original instructions to reproduce this error...
To add a little more context. We are seeing this error with grpc-go 1.48.0 golang 1.18 ``` rpc error: code = Internal desc = unexpected EOF" ``` client ``` grpc.WithDefaultCallOptions(...
Do you think that it would help even if in the case that we are setting Max to `math.MaxInt` as per above?
One more bit of context we see this right after `GOAWAY` from `MaxAge` . In a heavy traffic application. Generally speaking we are looking at about ~35000/TPS and the issue...
Thanks for the reply we currently have `MaxAgeGrace` set to `math.MaxInt64` to circumvent forceful closure of the stream. The result of those force closures was observed as. ``` rpc error:...
`unexpected EOF` is right after `GOAWAY` which made me feel like it was a possible issue with transparent retry but have not proved it. It ranges between 48 -> 72...
I will create a new issue for this but the whole reason we are using `ServerMaxConnectionAge` is because we would overflow the stream id every now and then. `invalid stream...