Merge pull request #535 from dandi/celery-beat

Add separate dyno for celery beat
dandi · Sep 30, 2021 · d21010f · d21010f
2 parents 4867478 + 3952ae7
commit d21010f
Showing 1 changed file with 2 additions and 4 deletions.
diff --git a/Procfile b/Procfile
@@ -1,6 +1,4 @@
 release: ./manage.py migrate
 web: gunicorn --bind 0.0.0.0:$PORT dandiapi.wsgi
-# We are using the -B flag to launch the beat scheduler within the worker thread
-# This means that we cannot have multiple workers, as they would all trigger beat events
-# The alternative would be a separate worker to drive the beat, which is costly at our current Heroku dyno tier
-worker: REMAP_SIGTERM=SIGQUIT celery --app dandiapi.celery worker --loglevel INFO -B
+worker: REMAP_SIGTERM=SIGQUIT celery --app dandiapi.celery worker --loglevel INFO
+celery-beat: REMAP_SIGTERM=SIGQUIT celery --app dandiapi.celery beat --loglevel INFO