Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>What you need is to set</p> <p>CELERY_ACKS_LATE = True</p> <p>Late ack means that the task messages will be acknowledged after the task has been executed, not just before, which is the default behavior. In this way if the worker crashes rabbit MQ will still have the message.</p> <p>Obviously of a total crash (Rabbit + workers) at the same time there is no way of recovering the task, except if you implement a logging on task start and task end. Personally I write in a mongodb a line every time a task start and another one when the task finish (independently form the result), in this way I can know which task was interrupted by analyzing the mongo logs.</p> <p>You can do it easily by overriding the methods <code>__call__</code> and <code>after_return</code> of the celery base task class.</p> <p>Following you see a piece of my code that uses a taskLogger class as context manager (with entry and exit point). The taskLogger class simply writes a line containing the task info in a mongodb instance.</p> <pre class="lang-py prettyprint-override"><code>def __call__(self, *args, **kwargs): """In celery task this function call the run method, here you can set some environment variable before the run of the task""" #Inizialize context managers self.taskLogger = TaskLogger(args, kwargs) self.taskLogger.__enter__() return self.run(*args, **kwargs) def after_return(self, status, retval, task_id, args, kwargs, einfo): #exit point for context managers self.taskLogger.__exit__(status, retval, task_id, args, kwargs, einfo) </code></pre> <p>I hope this could help</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload