net: DialContext returns "dial tcp <addr>: context deadline exceeded" error #23648
Labels
Comments
My guess is that the |
Closing as dup of #22724. |
Change https://golang.org/cl/103518 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Mar 29, 2018
Map the error returned when a dial is aborted from the context package error to the internal net package error. For example, context.Canceled errors map to errCanceled, and context.DeadlineExceeded errors map to poll.ErrTimeout. Fixes #23648 Change-Id: Idf9d3d08052d540740c0b054503aaed931dc5b1e Reviewed-on: https://go-review.googlesource.com/103518 Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.9.3 linux/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?What did you do?
A reverse proxy triggered a bunch of dial timeouts while connecting to a backend over a short period of time.
What did you expect to see?
A bunch of
"dial tcp <addr>: i/o timeout"
error messages.What did you see instead?
A reverse proxy logged a quick burst of
"dial tcp <addr>: context deadline exceeded"
errors. The errors originated from theDialContext
method a*net.Dialer
with aTimeout
value set.The text was updated successfully, but these errors were encountered: