1
我正在处理令人沮丧的错误 - 有时sidekiq不会开始处理作业。这是令人讨厌的间歇。Sidekiq - 间歇性非开始
发生时，sidekiq.log显示没有变化（并且正在运行）。队列大小保持为0.我猜它在Redis中迷路了。如果它很重要，我已经在同一台机器（不同的环境）上运行同一个应用程序的三个环境，我刚刚放入（但问题先于他们）。只有一个Redis在默认端口上运行。
我知道关于redis-cli MONITOR，但它发出的东西如此之快，而且有这么多，所以我很难弄清楚发生了什么。
1491479154.190069 [0 127.0.0.1:38763] "brpop" "queue:default" "2"
1491479154.289507 [0 127.0.0.1:38753] "brpop" "queue:default" "2"
1491479154.289544 [0 127.0.0.1:38752] "brpop" "queue:default" "2"
/// snip... many lines of these
1491479154.364985 [0 127.0.0.1:38772] "multi"
1491479154.365090 [0 127.0.0.1:38772] "incrby" "stat:processed" "0"
1491479154.365107 [0 127.0.0.1:38772] "incrby" "stat:processed:2017-04-06" "0"
1491479154.365128 [0 127.0.0.1:38772] "incrby" "stat:failed" "0"
1491479154.365133 [0 127.0.0.1:38772] "incrby" "stat:failed:2017-04-06" "0"
1491479154.365139 [0 127.0.0.1:38772] "del" "server.name:32533:6befea0f66c0:workers"
1491479154.365149 [0 127.0.0.1:38772] "expire" "server.name:32533:6befea0f66c0:workers" "60"
1491479154.365160 [0 127.0.0.1:38772] "exec"
1491479154.365896 [0 127.0.0.1:38772] "multi"
1491479154.365962 [0 127.0.0.1:38772] "sadd" "processes" "server.name:32533:6befea0f66c0"
1491479154.365977 [0 127.0.0.1:38772] "exists" "server.name:32533:6befea0f66c0"
1491479154.365987 [0 127.0.0.1:38772] "hmset" "server.name:32533:6befea0f66c0" "info" "{\"hostname\":\"server.name\",\"started_at\":1491373877.8700902,\"pid\":2217,\"tag\":\"demo\",\"concurrency\":25,\"queues\":[\"default\"],\"labels\":[],\"identity\":\"server.name:32533:6befea0f66c0\"}" "busy" "0" "beat" "1491479154.3655496" "quiet" "false"
1491479154.366035 [0 127.0.0.1:38772] "expire" "server.name:32533:6befea0f66c0" "60"
1491479154.366046 [0 127.0.0.1:38772] "rpop" "server.name:32533:6befea0f66c0-signals"
1491479154.366058 [0 127.0.0.1:38772] "exec"
1491479154.389484 [0 127.0.0.1:38751] "brpop" "queue:default" "2"
如何调试Redis和Sidekiq来解决这个问题？我想用grep管道，但我不能在redis-cli交互式外壳中做...
想法？
看起来像记忆问题！不回答，因为它不像一个“答案”，更像一个“领先”。当没有足够的内存时，我们很想知道是否有其他人看到Sidekiq/Redis以这种方式（默默地）失败。 –