Bug #17781: Resolv::DNS RequestID table allocations are never freed, causing DNS lookups to eventually hang - Ruby master - Ruby Issue Tracking System
bugs.ruby-lang.org/issues/1778

Sidekiqを長時間走らせておくと処理が止まる原因はこれかもわね…

@zundan Oh!!!

Is this the problem everyone's been having?! How did you manage to find it?

And I never noticed it because I'm still using 2.6.6 in production...

@Gargron I've just noticed this Ruby's bug in a PR to a work related code, while I personally haven't been able to reproduce Sidekiq hanging after a while as Heroku restarts processes every 24 hours.

@Gargron well, only thing Sidekiq log was claiming was that 'warn your redis connection...' but yes, on ruby 2.7.3
(ruby 2.7.3p183 (2021-04-05 revision 6847ee089d))
@zundan

@spla @zundan Could you confirm that you are affected by this? There's code you can run in the linked bug report

@Gargron @spla Yep. Reproduced locally on Ubuntu 20.04 and ruby 2.7.3p183 (2021-04-05 revision 6847ee089d) [x86_64-linux]

$ ruby /tmp/test.rb
Ran 65536 times

and top shows 99-100 %CPU for the ruby.

Also on a Hobby dyno on Heroku (waiting for a few minutes):

$ heroku run bash
~ $ which ruby
/app/bin/ruby
~ $ ruby --version
ruby 2.7.3p183 (2021-04-05 revision 6847ee089d) [x86_64-linux]
~ $ cat <<_END > test.rb
> require 'resolv'
> 65536.times { Resolv::DNS.new.getresource('www.example.net', Resolv::DNS::Resource::IN::A) }
> puts "Ran 65536 times"
> Resolv::DNS.new.getresource('www.example.net', Resolv::DNS::Resource::IN::A)
> puts "Ran 65537 times"
> _END
~ $ ruby test.rb
Ran 65536 times
^Z
[1]+ Stopped ruby test.rb
~ $ bg
[1]+ ruby test.rb &
~ $ top
:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
11 u6876 20 0 93216 34284 6100 R 99.7 0.1 1:59.79 ruby
:

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!