Redis::TimeoutError：連接超時錯誤 -Rails 緩存

Question

我們使用 redis(Elasticache) 作為我們的緩存存儲。由於 redis 連接超時，我們的應用程序正在崩潰。我們有三個應用程序服務器並使用 phusion 乘客。崩潰時大約有 200 個活動連接。

/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/connection/ruby.rb:55:in `rescue in _read_from_socket'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/connection/ruby.rb:48:in `_read_from_socket'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/connection/ruby.rb:41:in `gets'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/connection/ruby.rb:273:in `read'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:248:in `block in read'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:236:in `io'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:247:in `read'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:112:in `block in call'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:217:in `block (2 levels) in process'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:353:in `ensure_connected'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:207:in `block in process'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:292:in `logging'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:206:in `process'
/home/chillr/deploy/chillr-api/shared/vendor/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:112:in `call'

慢日志命令

1) 1) (integer) 6867375
2) (integer) 1486701507
3) (integer) 62008
4) 1) "eval"
   2) "for i, name in ipairs(redis.call('KEYS', 'cache:user_transaction_logs:*:9008245678')) do redis.call('DEL', name); end"
   3) "0"
 2) 1) (integer) 6867374
    2) (integer) 1486701507
    3) (integer) 61989
    4) 1) "KEYS"
       2) "cache:user_transaction_logs:*:9008245678"
 3) 1) (integer) 6867373
    2) (integer) 1486701507
    3) (integer) 61026
    4) 1) "eval"
       2) "for i, name in ipairs(redis.call('KEYS', 'cache:user_transaction_logs:*:8888662136')) do redis.call('DEL', name); end"
       3) "0"
 4) 1) (integer) 6867372
    2) (integer) 1486701507
    3) (integer) 61006
    4) 1) "KEYS"
       2) "cache:user_transaction_logs:*:8888662136"
 5) 1) (integer) 6867371
    2) (integer) 1486701507
    3) (integer) 63070
    4) 1) "eval"

我們用

• 彈性緩存。
• t2.medium Phusion 乘客

崩潰 175..200 時的連接數

GEM redis (3.2.1) redis-rails (5.0.1)

可以做什么

Answer 1

監控 Redis 服務器的當前資源使用情況。 暫時增加你的連接超時 redis 連接。

先試試這個清單

https://redis.io/topics/latency