ruby-on-rails - 在 Heroku 上使用 redis-rails 时出现 Redis::TimeoutError

Question

更新为包括 Redis/Resque 版本和堆​​栈跟踪(如下):

redis (3.0.4)
redis-namespace (1.3.0)
  redis (~> 3.0.0)
redis-store (1.1.2)
  redis (>= 2.2.0)
resque (1.24.1)
  mono_logger (~> 1.0)
  multi_json (~> 1.0)
  redis-namespace (~> 1.2)
  sinatra (>= 0.9.2)
  vegas (~> 0.1.2)
resque-scheduler (2.0.1)
  redis (>= 2.0.1)
  resque (>= 1.20.0)
  rufus-scheduler

---

我看到间歇性的 Redis::TimeoutError: Connection timed out在 Heroku 上，同时使用 Rails.cache.fetch 将中等大小的数组(~200 Fixnums)写入 Redis 存储。命令。

我也在使用 Resque。

我明白了here Redis::Client 可以接收超时选项，但我不知道在哪里将初始化选项传递给 Redis。

我正在使用标准的heroku resque.rb :

rails_root        = ENV['RAILS_ROOT'] || File.dirname(__FILE__) + '/../..'
rails_env         = ENV['RAILS_ENV'] || 'development'

resque_config     = YAML.load_file(rails_root + '/config/resque.yml')
ENV['REDIS_URI']  = resque_config[rails_env]
Resque.redis      = resque_config[rails_env]
Resque.inline     = rails_env == 'test'

require 'resque_scheduler'
require 'resque/scheduler'
require 'resque_scheduler/server'

Resque.schedule   = YAML.load_file(rails_root + '/config/resque-schedule.yml')

Resque.before_fork do
  defined?(ActiveRecord::Base) and
    ActiveRecord::Base.connection.disconnect!
end

Resque.after_fork do
  defined?(ActiveRecord::Base) and
    ActiveRecord::Base.establish_connection
end

我假设这里实例化了一个Redis客户端。这是与 production.rb 中实例化的客户端不同的客户端吗？ :

rails_root          = ENV['RAILS_ROOT'] || File.dirname(__FILE__) + '/../..'
rails_env           = ENV['RAILS_ENV'] || 'development'
resque_config = YAML.load_file(rails_root + '/config/resque.yml')
config.cache_store = :redis_store, resque_config[rails_env], { expires_in: 14.days }

选项哈希值是 Rails.cache据我所知的选项。这里是否实例化了一个新客户端？我怎样才能将选项传递给这个？

---

已更新以将此实验包含在 Heroku 控制台中，暗示它们是不同的客户端实例:

irb(main):002:0> Rails.cache
=> #<ActiveSupport::Cache::RedisStore:0x00000003860e18 @data=#<Redis client v3.0.4 for redis://spinyfin.redistogo.com:9485/0>, @options={:expires_in=>14 days}>
irb(main):003:0> Resque.redis.redis
=> #<Redis client v3.0.4 for redis://spinyfin.redistogo.com:9485/0>
irb(main):004:0> Rails.cache.instance_variable_get(:@data).object_id == Resque.redis.redis.object_id
=> false

---

堆栈跟踪:

Redis::TimeoutError: Connection timed out
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis/client.rb:208:in `rescue in io'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis/client.rb:206:in `io'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis/client.rb:214:in `read'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis/client.rb:84:in `block in call'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis/client.rb:187:in `block (2 levels) in process'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis/client.rb:295:in `ensure_connected'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis/client.rb:177:in `block in process'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis/client.rb:256:in `logging'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis/client.rb:176:in `process'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis/client.rb:84:in `call'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis.rb:644:in `block in setex'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis.rb:36:in `block in synchronize'
    from /app/vendor/ruby-1.9.3/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis.rb:36:in `synchronize'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-3.0.4/lib/redis.rb:643:in `setex'
    from /app/vendor/bundle/ruby/1.9.1/gems/redis-store-1.1.2/lib/redis/store/interface.rb:17:in `setex'
... 11 levels...
    from /app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.13/lib/active_support/cache.rb:299:in `fetch'
    ...SNIP...
    ...my code...
    ...SNIP...
    from /app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/relation/delegation.rb:6:in `each'
    from /app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/relation/delegation.rb:6:in `each'
    ...SNIP...
    ...my code...
    ...SNIP...
    from (irb):5
    from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/commands/console.rb:47:in `start'
    from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/commands/console.rb:8:in `start'
    from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/commands.rb:41:in `<top (required)>'
    from script/rails:6:in `require'
    from script/rails:6:in `<main>'irb(main):006:0>  !    Heroku client internal error.
 !    Search for help at: https://help.heroku.com
 !    Or report a bug at: https://github.com/heroku/heroku/issues/new

    Error:       Operation timed out (Errno::ETIMEDOUT)
    Backtrace:   /usr/local/heroku/ruby/lib/ruby/1.9.1/openssl/buffering.rb:121:in `sysread'
                 /usr/local/heroku/ruby/lib/ruby/1.9.1/openssl/buffering.rb:121:in `readpartial'
                 /Users/me/.heroku/client/lib/heroku/client/rendezvous.rb:69:in `block in start'
                 /Users/me/.heroku/client/lib/heroku/client/rendezvous.rb:53:in `loop'
                 /Users/me/.heroku/client/lib/heroku/client/rendezvous.rb:53:in `start'
                 /Users/me/.heroku/client/lib/heroku/command/run.rb:132:in `rendezvous_session'
                 /Users/me/.heroku/client/lib/heroku/command/run.rb:119:in `run_attached'
                 /Users/me/.heroku/client/lib/heroku/command/run.rb:24:in `index'
                 /Users/me/.heroku/client/lib/heroku/command.rb:206:in `run'
                 /Users/me/.heroku/client/lib/heroku/cli.rb:28:in `start'
                 /usr/local/heroku/bin/heroku:24:in `<main>'

    Command:     heroku run rails c
    Plugins:     heroku-redis-cli
    Version:     heroku-toolbelt/2.39.4 (x86_64-darwin10.8.0) ruby/1.9.3

Answer 1

“连接超时”消息意味着 redis-rb 在启动与 Redis 服务器的连接时遇到问题。通常，您只想在应用程序启动时初始化您的 Redis 连接。然而，由于 Resque fork (而不是使用像 Sidekiq 这样的线程)，它必须为每个单独的作业初始化一个新的 Redis 连接。

通常情况下，这不是问题，但 Heroku 在创建新的 Redis 连接时会出现间歇性问题。我在各种语言/客户端库/Redis 主机中都看到过这个问题，除了减少您创建的 Redis 连接数量之外，缓解该问题的唯一方法是在 Resque.after_fork block 中自动重试连接到 Redis 几次。 (例如，如果您尝试了 3 次，则捕获超时错误并重试或重新引发异常)