https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112018-08-16T08:57:57ZRuby Issue Tracking SystemRuby master - Bug #14997: Socket connect timeout exceeds the timeout value for https://bugs.ruby-lang.org/issues/14997?journal_id=735572018-08-16T08:57:57Zmaciej.mensfeld (Maciej Mensfeld)maciej@mensfeld.pl
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/73557/diff?detail_id=49710">diff</a>)</li></ul> Ruby master - Bug #14997: Socket connect timeout exceeds the timeout value for https://bugs.ruby-lang.org/issues/14997?journal_id=736912018-08-24T14:47:48Zmaciej.mensfeld (Maciej Mensfeld)maciej@mensfeld.pl
<ul></ul><p>If anyone is actually willing to confirm, that it is indeed an unwanted / unexpected behavior, I offer to fix it.</p>
<p>It could be fixed by tracking how much of the time "pool" has been used and lowering the timeout value appropriate for the next attempts. That would guarantee, that we would never exceed the timeout.</p>
<p>I think this is the most elegant solution.</p> Ruby master - Bug #14997: Socket connect timeout exceeds the timeout value for https://bugs.ruby-lang.org/issues/14997?journal_id=790222019-07-02T10:58:15Ztenderlovemaking (Aaron Patterson)tenderlove@ruby-lang.org
<ul></ul><p>This really sounds like a bug to me. Please make a patch and I will apply it.</p> Ruby master - Bug #14997: Socket connect timeout exceeds the timeout value for https://bugs.ruby-lang.org/issues/14997?journal_id=802302019-07-30T03:35:11ZGlass_saga (Masaki Matsushita)glass.saga@gmail.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/15553">Feature #15553</a>: Addrinfo.getaddrinfo supports timeout</i> added</li></ul> Ruby master - Bug #14997: Socket connect timeout exceeds the timeout value for https://bugs.ruby-lang.org/issues/14997?journal_id=827952019-11-26T14:03:10Zkirs (Kir Shatrov)shatrov@me.com
<ul></ul><p>tenderlovemaking (Aaron Patterson) wrote:</p>
<blockquote>
<p>This really sounds like a bug to me. Please make a patch and I will apply it.</p>
</blockquote>
<p>Do you mind taking a look at <a href="https://github.com/ruby/ruby/pull/1806" class="external">https://github.com/ruby/ruby/pull/1806</a>? Based on my testing it's solving the problem.</p>
<p>Together with <a href="https://bugs.ruby-lang.org/issues/15553" class="external">https://bugs.ruby-lang.org/issues/15553</a> (already merged), many of us at Shopify would really love to see that fixed in 2.7 as it would improve resiliency and avoid Ruby processes to hang for 10s (default resolv timeout) when DNS is experiencing issues.</p> Ruby master - Bug #14997: Socket connect timeout exceeds the timeout value for https://bugs.ruby-lang.org/issues/14997?journal_id=873302020-08-31T21:38:14Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>I believe this timeout issue is now solved by the Socket.tcp :resolv_timeout option, introduced in <a class="changeset" title="Support timeout for Addrinfo Addrinfo.getaddrinfo and .foreach now accepts :timeout in seconds a..." href="https://bugs.ruby-lang.org/projects/ruby-master/repository/git/revisions/6382f5cc91ac9e36776bc854632d9a1237250da7">6382f5cc91ac9e36776bc854632d9a1237250da7</a>.</p>