芹菜错过了心跳(on_node_lost) [英] celery missed heartbeat (on_node_lost)

查看:95
本文介绍了芹菜错过了心跳(on_node_lost)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我刚刚升级到celery 3.1,现在我在我的日志中看到了这一点::

I just upgraded to celery 3.1 and now I see this i my logs ::

on_node_lost - INFO - missed heartbeat from celery@queue_name for every queue/worker in my cluster.

根据文档 BROKER_HEARTBEAT 关闭

我应该显式设置 BROKER_HEARTBEAT = 0 还是还有其他东西我应该检查吗?

Should I explicitly set BROKER_HEARTBEAT=0 or is there something else that I should be checking?

推荐答案

看到了同样的事情,并且注意到日志文件中有几件事。

Saw the same thing, and noticed a couple of things in the log files.

1)在日志开始时有关于时间漂移的消息,偶尔还会丢失心跳。

1) There were messages about time drift at the start of the log and occasional missed heartbeats.

2)

3)漂移消息消失后​​,系统没有任何变化。 ..他们才停止露面。

3) There were no changes to the system when the drift messages went away... They just stopped showing up.

我认为漂移本身可能就是问题所在。

I figured that the drift itself was likely the problem itself.

在所有涉及的服务器上同步时间之后,这些消息消失了。对于ubuntu,请将ntpdate作为cron或ntpd运行。

After syncing the time on all the servers involved these messages went away. For ubuntu, run ntpdate as a cron or ntpd.

这篇关于芹菜错过了心跳(on_node_lost)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆