|
|
|
|
|
|
by rmnclmnt
1157 days ago
|
|
|
Great read, thanks! I haven't heavily used Celery anymore for the past few years, but I remember trying to setup a HA Celery Beat schedule process with Kubernetes in 2019 and hitting this exact same issue! There was an alternative scheduler[1] storing its state in Redis instead of a local file, after a few fixes it was working pretty well: multiple beat processes running concurrently and not firing twice a scheduled task. Don't know if that still works though. [1] https://github.com/mixkorshun/celery-beatx |
|
|