mirror of
https://github.com/discourse/discourse.git
synced 2024-12-12 13:13:40 +08:00
66982c7800
The Rails 5.2 connection reaper appears to be leaking threads this is a quick fix to stop it, though we need to make sure we never leak connection pools as well.
19 lines
673 B
Ruby
19 lines
673 B
Ruby
# Discourse ships with a connection reaper
|
|
# this patch ensures that the connection reaper never runs in Rails
|
|
#
|
|
# In Rails 5.2 the connection reaper is "per-pool" this means it can bloat
|
|
# threads quite a lot in a multisite
|
|
#
|
|
# Note, the "correct" way is to set this in the spec, however due to multisite
|
|
# getting reaper_interval=0 into all the specs is not going to be trivial
|
|
# when we eventually do that we can remove this patch
|
|
|
|
if !defined? ActiveRecord::ConnectionAdapters::ConnectionPool::Reaper
|
|
raise "Can not find connection Reaper class, this patch will no longer work!"
|
|
end
|
|
|
|
class ActiveRecord::ConnectionAdapters::ConnectionPool::Reaper
|
|
def run
|
|
end
|
|
end
|