Re:Celery, non-blocking code and quest against coroutines
by jvoorhis on Thursday June 09, 2016 @12:55PM
(#11870612)
In my experience, celery takes some hand holding to stay alive. I generally configure it to recycle workers after N tasks, in addition to a hard timeout on tasks. I've also found in my configuration, using RabbitMQ as the bus, workers can become non-responsive after receiving too large a message.
[ Parent
| on HN ]
There are no comments on this comment yet.