I am doing the following upgrade on celery in my django project.
我正在我的django项目中对芹菜进行以下升级。
django-celery==3.0.11 FROM 2.1.2
django-celery == 3.0.11 FROM 2.1.2
CELERY == 3.0.13 FROM celery==2.1.4
CELERY == 3.0.13来自芹菜== 2.1.4
My questions is will all my tasks continue to queue up and continue or will some tasks get dropped in the processes? I want to make sure nothing is getting skipped or looked over during the upgrade.
我的问题是，我的所有任务是否会继续排队并继续，或者某些任务会在流程中被删除？我想确保在升级过程中没有任何内容被跳过或查看过。
1 个解决方案
#1
0
I don't have any experience in upgrading celery and django-celery although I am using both for an app in production. But as per my understanding, as long as the message broker (rabbitmq in my case) is running, the tasks will be queued up and given to the workers when they are up again.
我没有任何升级芹菜和django-celery的经验，尽管我在生产中同时使用它们。但根据我的理解，只要消息代理（在我的情况下是rabbitmq）正在运行，任务就会排队等待，并在工作人员再次启动时提供给工作人员。
So it would just be a matter of stopping the celery workers, upgrading both celery and django-celery and starting the workers again.
因此，只需停止芹菜工人，升级芹菜和django芹菜，再次启动工人。
Although before proceeding, you might want to find out if there are any known issues during upgrading from celery 2.x to 3.x in order to avoid any substantial downtime. May be try this on a dev or staging machine first if possible?
虽然在继续之前，您可能想知道在从celery 2.x升级到3.x期间是否存在任何已知问题，以避免任何实质性的停机时间。如果可能的话，可以首先在dev或staging机器上尝试这个吗？
#1
0
I don't have any experience in upgrading celery and django-celery although I am using both for an app in production. But as per my understanding, as long as the message broker (rabbitmq in my case) is running, the tasks will be queued up and given to the workers when they are up again.
我没有任何升级芹菜和django-celery的经验，尽管我在生产中同时使用它们。但根据我的理解，只要消息代理（在我的情况下是rabbitmq）正在运行，任务就会排队等待，并在工作人员再次启动时提供给工作人员。
So it would just be a matter of stopping the celery workers, upgrading both celery and django-celery and starting the workers again.
因此，只需停止芹菜工人，升级芹菜和django芹菜，再次启动工人。
Although before proceeding, you might want to find out if there are any known issues during upgrading from celery 2.x to 3.x in order to avoid any substantial downtime. May be try this on a dev or staging machine first if possible?
虽然在继续之前，您可能想知道在从celery 2.x升级到3.x期间是否存在任何已知问题，以避免任何实质性的停机时间。如果可能的话，可以首先在dev或staging机器上尝试这个吗？