Problem
CELERY_BEAT_SCHEDULE in src/settings/base.py contains an entry that
publishes competitions.tasks.refresh_compute_worker_health every 60s,
but the task is not defined anywhere in the codebase.
Effect
Every minute, Beat publishes a task name the worker cannot resolve,
producing repeated NotRegistered / KeyError errors on the
site_worker prefork consumer. This pollutes logs and, under certain
conditions, can break the consumer channel.
Problem
CELERY_BEAT_SCHEDULEinsrc/settings/base.pycontains an entry thatpublishes
competitions.tasks.refresh_compute_worker_healthevery 60s,but the task is not defined anywhere in the codebase.
Effect
Every minute, Beat publishes a task name the worker cannot resolve,
producing repeated
NotRegistered/KeyErrorerrors on thesite_worker prefork consumer. This pollutes logs and, under certain
conditions, can break the consumer channel.