On Wednesday, September 2, 2015 at 8:29:17 AM UTC-4, kartik wrote:

Calls to my server come from other servers(and not browser). Secondly, my server doesn't close the connection ever(for performance reasons), but clients do(whenever response time exceeds, say 200ms).

I haven't configured any "ReadTimeout"(or writeTimeout) in my server, I wonder why these goroutines are waiting for days.

Has anyone else faced a similar problem? Does this occur when the client closes the connection while the goroutine is still reading? The memory on my server has been increasing steadily as the # of goroutines that enter into this "wait" state keeps on increasing.
There's not much we can do without any code to see, but most likely it's
not the server, and the http client is keeping connections open. Either
you're failing to close every request and leaking connections, or it's
possible that you're requesting from thousands of hosts, and maintaining a
lot of keepalive connections.

You should also still have timeouts on everything if you have a long
running service. You can't guarantee the behavior of every client and
server you're connected to.

You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 3 of 14 | next ›
Discussion Overview
groupgolang-nuts @
postedSep 2, '15 at 12:29p
activeSep 4, '15 at 1:48p



site design / logo © 2021 Grokbase