celery

问题 How to run celery as Daemon service in ubuntu instead of running " celery -A projname worker -l info " command each time. I am using celery 3.1.8 version.... 回答1: You can make celery into a daemon with the init.d script from celery's repo (Save it to /etc/init.d/ ). You will also need to create a configuration file for the script to load in /etc/default/celeryd . Here's the full celery doc. 回答2: You can make celery worker as a daemon using a tool called supervisord. It's a simple process

问题 How to run celery as Daemon service in ubuntu instead of running " celery -A projname worker -l info " command each time. I am using celery 3.1.8 version.... 回答1: You can make celery into a daemon with the init.d script from celery's repo (Save it to /etc/init.d/ ). You will also need to create a configuration file for the script to load in /etc/default/celeryd . Here's the full celery doc. 回答2: You can make celery worker as a daemon using a tool called supervisord. It's a simple process

问题 How to run celery as Daemon service in ubuntu instead of running " celery -A projname worker -l info " command each time. I am using celery 3.1.8 version.... 回答1: You can make celery into a daemon with the init.d script from celery's repo (Save it to /etc/init.d/ ). You will also need to create a configuration file for the script to load in /etc/default/celeryd . Here's the full celery doc. 回答2: You can make celery worker as a daemon using a tool called supervisord. It's a simple process

问题 According to Celery's documentation, we should not use the terminate option in revoke() function to cancel an executing task: The terminate option is a last resort for administrators when a task is stuck. It’s not for terminating the task, it’s for terminating the process that’s executing the task, and that process may have already started processing another task at the point when the signal is sent, so for this reason you must never call this programmatically. http://docs.celeryproject.org

问题 According to Celery's documentation, we should not use the terminate option in revoke() function to cancel an executing task: The terminate option is a last resort for administrators when a task is stuck. It’s not for terminating the task, it’s for terminating the process that’s executing the task, and that process may have already started processing another task at the point when the signal is sent, so for this reason you must never call this programmatically. http://docs.celeryproject.org

问题 I have created a celery app with following directory structure (as given in celery site): proj |-- celery.py |-- celery.pyc |-- __init__.py |-- __init__.pyc |-- tasks.py `-- tasks.pyc Following are contents of celery.py from __future__ import absolute_import from celery import Celery app = Celery('proj', broker='amqp://rabbitmquser:<my_passowrd>@localhost:5672/localvhost', #backend='amqp://', include=['proj.tasks']) # Optional configuration, see the application user guide. app.conf.update(

问题 As I can see in top utility celery procecess consume a lot of CPU time. So I want to profile it. I can do it manually on developer machine like so: python -m cProfile -o test-`date +%Y-%m-%d-%T`.prof ./manage.py celeryd -B But to have accurate timings I need to profile it on production machine. On that machine (Fedora 14) celery is launched by init scripts. E.g. service celeryd start I have figured out these scripts eventually call manage.py celeryd_multi eventually. So my question is how can

问题 As I can see in top utility celery procecess consume a lot of CPU time. So I want to profile it. I can do it manually on developer machine like so: python -m cProfile -o test-`date +%Y-%m-%d-%T`.prof ./manage.py celeryd -B But to have accurate timings I need to profile it on production machine. On that machine (Fedora 14) celery is launched by init scripts. E.g. service celeryd start I have figured out these scripts eventually call manage.py celeryd_multi eventually. So my question is how can

问题 I have installed Celery with RabbitMQ. Problem is that for every result that is returned, Celery will create in the Rabbit, queue with the task's ID in the exchange celeryresults. I still want to have results, but on ONE queue. my celeryconfig: from datetime import timedelta OKER_URL = 'amqp://' CELERY_RESULT_BACKEND = 'amqp' #CELERY_IGNORE_RESULT = True CELERY_TASK_SERIALIZER = 'json' CELERY_RESULT_SERIALIZER = 'json' CELERY_ACCEPT_CONTENT=['json', 'application/json'] CELERY_TIMEZONE =

问题 Suppose I have a model Event . I want to send a notification (email, push, whatever) to all invited users once the event has elapsed. Something along the lines of: class Event(models.Model): start = models.DateTimeField(...) end = models.DateTimeField(...) invited = models.ManyToManyField(model=User) def onEventElapsed(self): for user in self.invited: my_notification_backend.sendMessage(target=user, message="Event has elapsed") Now, of course, the crucial part is to invoke onEventElapsed