You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking for a way to stagger CELERY_BEAT_SCHEDULE tasks to run at different times per tenant, rather than all tenants executing tasks simultaneously
Celery Version: 5.4.0
Celery-Beat Version: 2.5.0
Exact steps to reproduce the issue:
Define CELERY_BEAT_SCHEDULE with multiple tasks that run at regular intervals.
Use this setup across multiple tenants. (django-tenants)
Observe that all tenants execute tasks simultaneously, causing high resource load
Detailed information
This issue has been cross-posted on tenants-schemas-celery, but checking here as well to explore any solutions specific to django-celery-beat.
When tasks run at the same intervals across all tenants, it creates a high resource load as the number of tenants grows. A solution to vary task execution times slightly per tenant, without complex configurations or major structural changes, would be ideal.
Any guidance or examples for implementing this kind of staggered scheduling would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered:
Summary:
Looking for a way to stagger
CELERY_BEAT_SCHEDULE
tasks to run at different times per tenant, rather than all tenants executing tasks simultaneouslyExact steps to reproduce the issue:
CELERY_BEAT_SCHEDULE
with multiple tasks that run at regular intervals.django-tenants
)Detailed information
This issue has been cross-posted on tenants-schemas-celery, but checking here as well to explore any solutions specific to
django-celery-beat
.When tasks run at the same intervals across all tenants, it creates a high resource load as the number of tenants grows. A solution to vary task execution times slightly per tenant, without complex configurations or major structural changes, would be ideal.
Any guidance or examples for implementing this kind of staggered scheduling would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered: