[rabbitmq-discuss] Temporary queue being made when task fails
sidchilling at gmail.com
Mon Aug 22 15:16:59 BST 2011
OK I got the solution.
CELERY_IGNORE_RESULT = True should do the trick for Celery 2.2. The problem
with my configuration was that I was using
CELERY_STORE_ERRORS_EVEN_IF_IGNORED = True which was negating the ignore
Now, the extra queues are not being formed anymore.
Thanks. Just wanted to ask - is there any side-effects of this change of
configuration which I should check?
On Mon, Aug 22, 2011 at 7:15 PM, Siddharth Saha <sidchilling at gmail.com>wrote:
> Yes, I am using Celery2.2 and upgrading it is not the solution I'm looking
> for now. May be in the near future :)
> But, I am already using CELERY_IGNORE_RESULT = True but that also it now
> solving the problem. I've been using this configuration already.
> On Mon, Aug 22, 2011 at 7:11 PM, Ask Solem <ask at rabbitmq.com> wrote:
>> On 22 Aug 2011, at 14:37, Siddharth Saha wrote:
>> > From the doc, it seems the default option of CELERY_RESULT_BACKEND is
>> disabled. And if you write -
>> > CELERY_RESULT_BACKEND = "disabled"
>> > in the celeryconfig.py file, then celery does not start with the error -
>> > ValueError: Unknown result backend: 'disabled'. Did you spell it
>> correctly? (Couldn't import 'disabled': Empty module name)
>> > From the doc, I do not find the disabled option for
>> CELERY_RESULT_BACKEND. The available options are -
>> > • database
>> > • cache
>> > • mongodb
>> > • redis
>> > • tyrant
>> > • amqp
>> > And in my case, I am not setting this option at all, so it must be
>> disabled by default. Is there anything else which I might be missing?
>> Please upgrade to 2.3, or set CELERY_IGNORE_RESULT=True.
> -Siddharth Saha
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss