celerybeat

问题 There is not much documentation available for the actual usage of django celery.backend_cleanup Let's assume i have following 4 tasks scheduled with different interval Checking DatabaseScheduler Logs I had found that only Task1 is executing on interval. [2018-12-28 11:21:08,241: INFO/MainProcess] Writing entries... [2018-12-28 11:24:08,778: INFO/MainProcess] Writing entries... [2018-12-28 11:27:09,315: INFO/MainProcess] Writing entries... [2018-12-28 11:28:32,948: INFO/MainProcess] Scheduler:

问题 I have ~250,000 recurring tasks each day; about a fifth of which might be updated with different scheduled datetimes each day. Can this be done efficiently in Celery? - I am worried about this from celery's beat.py: def tick(self): """Run a tick, that is one iteration of the scheduler. Executes all due tasks. """ remaining_times = [] try: for entry in values(self.schedule): next_time_to_run = self.maybe_due(entry, self.publisher) if next_time_to_run: remaining_times.append(next_time_to_run)

问题 Out of the blue I get the following error when trying to start my dev server with celery and celery beat. One day this thing works next day it doesn't, I haven't changed anything that could explain this. I start my server using foreman and a Procfile.dev like so: Procfile: web: python manage.py runserver celeryd: python manage.py celeryd -E -B --loglevel=INFO --concurrency=3 worker: python manage.py celerycam Command: foreman start -f Procfile.dev Like I said this never gave any errors.

问题 I am running Django + Celery + RabbitMQ. After modifying some task names I started getting "unregistered task" KeyErrors, even after removing tasks with this key from the Periodic tasks table in Django Celery Beat and restarting the Celery worker. It turns out Celery / RabbitMQ tasks are persistent. I eventually resolved the issue by reimplementing the legacy tasks as dummy methods. In future, I'd prefer not to purge the queue, restart the worker or reimplement legacy methods. Instead I'd

问题 Till now I had only worked with Celery tasks defined as functions. I used to define their periodicity in the CELERYBEAT_SCHEDULE parameter. Like this: from datetime import timedelta CELERYBEAT_SCHEDULE = { 'add-every-30-seconds': { 'task': 'tasks.add', 'schedule': timedelta(seconds=30), 'args': (16, 16) }, } Now I am trying to use class-based tasks, like this one: class MyTask(Task): """My Task.""" def run(self, source, *args, **kwargs): """Run the celery task.""" logger.info("Hi!") My

问题 I am just getting started with celery,trying to run a periodic task. Configured *rabbitmq** added celeryconfig.py. And added following code in tasks.py: from celery.decorators import periodic_task from datetime import timedelta @periodic_task(run_every=timedelta(seconds=2)) def every_2_seconds(): print("Running periodic task!") Now when I start celerybeat by typing "celerybeat" in my terminal it starts to run with follwing message celerybeat celerybeat v3.0.3 (Chiastic Slide) is starting. __

问题 Everything worked perfectly fine until: celery beat v3.1.18 (Cipater) is starting. __ - ... __ - _ Configuration -> . broker -> amqp://user:**@staging-api.user-app.com:5672// . loader -> celery.loaders.app.AppLoader . scheduler -> celery.beat.PersistentScheduler . db -> /tmp/beat.db . logfile -> [stderr]@%INFO . maxinterval -> now (0s) [2015-09-25 17:29:24,453: INFO/MainProcess] beat: Starting... [2015-09-25 17:29:24,457: CRITICAL/MainProcess] beat raised exception <class 'EOFError'>:

问题 I am using celerybeat on Heroku with RedisToGo Nano addon There is one web dyno and one worker dyno The celerybeat worker is set to perform a task every minute. The problem is: Whenever I deploy a new commit, dynos restart, and I get this error 2014-02-27T13:19:31.552352+00:00 app[worker.1]: Traceback (most recent call last): 2014-02-27T13:19:31.552352+00:00 app[worker.1]: File "/app/.heroku/python/lib/python2.7/site-packages/celery/worker/consumer.py", line 389, in start 2014-02-27T13:19:31

问题 I am using celery beat to schedule some tasks. I'm able to use the CELERY_TIMEZONE setting to schedule the tasks using the crontab schedule and it runs at the scheduled time in the mentioned time zone. But I want to be able to setup multiple such tasks for different timezones in the same application (single django settings.py). I know which task needs to run in what timezone when the task is being scheduled. Is it possible to specify a different timezone for each of the tasks? I'm using

问题 I need to update the solr index on a schedule with the command: (env)$ ./manage.py update_index I've looked through the Celery docs and found info on scheduling, but haven't been able to find a way to run a django management command on a schedule and inside a virtualenv. Would this be better run on a normal cron? And if so how would I run it inside the virtualenv? Anyone have experience with this? Thanks for the help! 回答1: To run your command periodically from a cron job, just wrap the