Clear old locks when server starts?

If the server goes down while a task is running and has acquired a lock, the lock is still in place when the server comes back up. It isn’t released until the default timeout has expired and there doesn’t seem to be any clean mechanism for dealing with this.

A similar project to this called celery-singleton has a clear_locks API that removes any locks. This can be called when workers are first ready.

from celery.signals import worker_ready
from celery_singleton import clear_locks
from somewhere import celery_app

@worker_ready()
def unlock_all(**kwargs):
    clear_locks(celery_app)

Does such a mechanism exist for this project? Maybe I’m missing it. If it doesn’t exist, would this be a welcome feature?

[CalebFenton]

Btw, if anyone is curious, this is really easy to do without any special API call:

@signals.worker_ready.connect
def unlock_all(**kwargs):
    lock_keys = redis_db.get('qo_*')
    redis_db.delete(*lock_keys)

[chpmrc]

How would the proposed solution work with multiple workers connecting to the same backend? For example worker1 might set a lock, worker2 might crash, reinitialize and remove all locks on connect, which is obviously not ok.

EDIT: actually, now that I think about, the worst case seems to be an overlap of at most 2 tasks (assuming only one lock key is used), not a big deal.