Sam Batschelet comments

Results 50 comments of


Sam Batschelet

Support for unix abstract sockets

cc @LucioFranco it appears that you reviewed the original PR. Thanks in advance.

gRPC connection closing with unexpected EOF on high-latency connections

@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...

gRPC connection closing with unexpected EOF on high-latency connections

cc @dfawley please reopen?

gRPC connection closing with unexpected EOF on high-latency connections

> 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...

gRPC connection closing with unexpected EOF on high-latency connections

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(...

gRPC connection closing with unexpected EOF on high-latency connections

Do you think that it would help even if in the case that we are setting Max to `math.MaxInt` as per above?

gRPC connection closing with unexpected EOF on high-latency connections

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...

gRPC connection closing with unexpected EOF on high-latency connections

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:...

gRPC connection closing with unexpected EOF on high-latency connections

`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...

gRPC connection closing with unexpected EOF on high-latency connections

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...