gpt4 book ai didi

ruby-on-rails - Redis EXECABORT 事务因先前的错误而被丢弃。 (Redis::CommandError) Sidekiq 错误

转载 作者:可可西里 更新时间:2023-11-01 11:13:25 26 4
gpt4 key购买 nike

我正在为一些长时间运行的作业使用 sidekiq 3.4.2 和 redis 3.0.3,大约两到四个小时后,我收到以下错误:

ERROR: heartbeat: EXECABORT Transaction discarded because of previous errors.

EXECABORT Transaction discarded because of previous errors. /home/deployer/apps/wripl-capture/shared/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/pipeline.rb:79:in finish'
/home/deployer/apps/wripl-capture/shared/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:149:in
block in call_pipeline' /home/deployer/apps/wripl-capture/shared/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:279:in with_reconnect'
/home/deployer/apps/wripl-capture/shared/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:147:in
call_pipeline' /home/deployer/apps/wripl-capture/shared/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis.rb:2182:in block in multi'
/home/deployer/apps/wripl-capture/shared/bundle/ruby/2.2.0/gems/redis-3.2.1/lib/redis.rb:37:in
block in synchronize' /usr/local/rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'

除非我重新启动 sidekiq,否则一切都会被杀死(没有排队的作业运行),这不是我需要做的。

知道发生了什么吗?

最佳答案

这也可能由于空的 multi 命令而发生。

运行 redis-cli monitor 我看到了

1546789398.881549 [0 the-ip] "multi"
1546789398.881575 [0 the-ip] "exec"

在执行 multi 之前,请确保您至少有 1 个命令要在事务上执行。

关于ruby-on-rails - Redis EXECABORT 事务因先前的错误而被丢弃。 (Redis::CommandError) Sidekiq 错误,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/32724410/

26 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com