Applied workaround for issue #2656: Disable new Rails database connection reaping functionality until the Thread-Zombie issue is resolved: https://github.com/rails/rails/issues/33600 .
This commit is contained in:
parent
eafe412d87
commit
c09e698709
2 changed files with 23 additions and 0 deletions
|
@ -1,6 +1,7 @@
|
||||||
require_relative 'boot'
|
require_relative 'boot'
|
||||||
|
|
||||||
require 'rails/all'
|
require 'rails/all'
|
||||||
|
require_relative 'issue_2656_workaround_for_rails_issue_33600'
|
||||||
|
|
||||||
# DO NOT REMOVE THIS LINE - see issue #2037
|
# DO NOT REMOVE THIS LINE - see issue #2037
|
||||||
Bundler.setup
|
Bundler.setup
|
||||||
|
|
22
config/issue_2656_workaround_for_rails_issue_33600.rb
Normal file
22
config/issue_2656_workaround_for_rails_issue_33600.rb
Normal file
|
@ -0,0 +1,22 @@
|
||||||
|
# This temporary workaround for issue #2656.
|
||||||
|
# The root cause is an issue in Rails: https://github.com/rails/rails/issues/33600
|
||||||
|
# It disables database connnection reaping by setting `reaping_frequency` to 0 for each environment in the config/database.yml file.
|
||||||
|
# It restores the DB connection reaping behavior Rails > 5.2 had.
|
||||||
|
# It was proposed in a comment on the Rails issue: https://github.com/rails/rails/issues/33600#issuecomment-415395901
|
||||||
|
# It was confirmed by @matthewd (a Rails core maintainer) in another comment: https://github.com/rails/rails/issues/33600#issuecomment-415400522
|
||||||
|
module Rails
|
||||||
|
class Application
|
||||||
|
class Configuration < ::Rails::Engine::Configuration
|
||||||
|
|
||||||
|
alias database_configuration_original database_configuration
|
||||||
|
|
||||||
|
def database_configuration
|
||||||
|
database_configuration_original&.transform_values do |config|
|
||||||
|
config.merge(
|
||||||
|
'reaping_frequency' => 0
|
||||||
|
)
|
||||||
|
end
|
||||||
|
end
|
||||||
|
end
|
||||||
|
end
|
||||||
|
end
|
Loading…
Reference in a new issue