Spurious server log produced when client closes birectional stream

[geeknoid]

I have a client/server setup using bidirectional streaming. When the client calls stream.CloseSend and then immediately closes the underlying TCP connection, the server produces the following spurious log entry:

http2_server.go:320] transport: http2Server.HandleStreams failed to read frame: read tcp [::1]:9091->[::1]:38241: read: connection reset by peer

After this, everything works fine. If I insert a 1 second delay on the client between the call to CloseSend and the call to close the socket, then the log message doesn't get emitted.

This message is polluting our logs, that's why I'd like to get rid of it.

This is with Go 1.7.4

[MakMukhi]

Hey Martin, We're working on adding levels to logging. This will reduce the verbosity for more restrictive levels. The PR is under its way. However, I don't have a time line for you at this moment since the guy working on this is out on vacation. Regards, Mak

…

On Tue, Jan 31, 2017 at 5:49 PM, Martin Taillefer ***@***.***> wrote: I have a client/server setup using bidirectional streaming. When the client calls stream.CloseSend and then immediately closes the underlying TCP connection, the server produces the following spurious log entry: http2_server.go:320] transport: http2Server.HandleStreams failed to read frame: read tcp [::1]:9091->[::1]:38241: read: connection reset by peer After this, everything works fine. If I insert a 1 second delay on the client between the call to CloseSend and the call to close the socket, then the log message doesn't get emitted. This message is polluting our logs, that's why I'd like to get rid of it. This is with Go 1.7.4 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1059>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATtnR2aPvnyGNBwF3AXg_qZbnIgyoOWkks5rX-SMgaJpZM4LzZ2S> .

[geeknoid]

Thanks for the follow-up. For now, I've added a 50ms delay in our test client code to eliminate the issue internally for us. But that's not a good long-term story of course...

…

On Wed, Feb 1, 2017 at 10:14 AM, MakMukhi ***@***.***> wrote: Hey Martin, We're working on adding levels to logging. This will reduce the verbosity for more restrictive levels. The PR is under its way. However, I don't have a time line for you at this moment since the guy working on this is out on vacation. Regards, Mak On Tue, Jan 31, 2017 at 5:49 PM, Martin Taillefer < ***@***.***> wrote: > I have a client/server setup using bidirectional streaming. When the > client calls stream.CloseSend and then immediately closes the underlying > TCP connection, the server produces the following spurious log entry: > > http2_server.go:320] transport: http2Server.HandleStreams failed to read > frame: read tcp [::1]:9091->[::1]:38241: read: connection reset by peer > > After this, everything works fine. If I insert a 1 second delay on the > client between the call to CloseSend and the call to close the socket, then > the log message doesn't get emitted. > > This message is polluting our logs, that's why I'd like to get rid of it. > > This is with Go 1.7.4 > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#1059>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/ATtnR2aPvnyGNBwF3AXg_ qZbnIgyoOWkks5rX-SMgaJpZM4LzZ2S> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1059 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVucHWb4v7ziBT-DB6YMOeZnBfLBZjpFks5rYMuKgaJpZM4LzZ2S> .