Fix for Resque forking might cause stuck workers for the threaded Sidekiq.
This commit is contained in:
parent
fe059b6c4b
commit
994fe9fd31
1 changed files with 0 additions and 36 deletions
|
@ -1,36 +0,0 @@
|
||||||
# from http://gist.github.com/238999
|
|
||||||
#
|
|
||||||
# If your workers are inactive for a long period of time, they'll lose
|
|
||||||
# their MySQL connection.
|
|
||||||
#
|
|
||||||
# This hack ensures we re-connect whenever a connection is
|
|
||||||
# lost. Because, really. why not?
|
|
||||||
#
|
|
||||||
# Stick this in RAILS_ROOT/config/initializers/connection_fix.rb (or somewhere similar)
|
|
||||||
#
|
|
||||||
# From:
|
|
||||||
# http://coderrr.wordpress.com/2009/01/08/activerecord-threading-issues-and-resolutions/
|
|
||||||
|
|
||||||
if defined?(ActiveRecord::ConnectionAdapters::Mysql2Adapter)
|
|
||||||
|
|
||||||
module ActiveRecord::ConnectionAdapters
|
|
||||||
|
|
||||||
class Mysql2Adapter
|
|
||||||
alias_method :execute_without_retry, :execute
|
|
||||||
|
|
||||||
def execute(*args)
|
|
||||||
execute_without_retry(*args)
|
|
||||||
rescue ActiveRecord::StatementInvalid => e
|
|
||||||
if e.message =~ /server has gone away/i
|
|
||||||
warn "Server timed out, retrying"
|
|
||||||
reconnect!
|
|
||||||
retry
|
|
||||||
else
|
|
||||||
raise e
|
|
||||||
end
|
|
||||||
end
|
|
||||||
end
|
|
||||||
|
|
||||||
end
|
|
||||||
|
|
||||||
end
|
|
Loading…
Reference in a new issue