persistance for revoked tasks ?

[urzbs]

Hey there,

when calling

app.control.revoke(task_id, terminate=True)

while all workers are offline, the revocation information is lost - So now, when you start your workers, they will work on your previously revoked task...

This is a real problem for distrubuted worker clusters, where you dont have crontrol if they are currently running or not.

is there a setting or a mechanism that makes revocation persistent / deletes task from queue?

Kind regards

[urzbs]

sorry might be the wrong place to ask a generic celery question