Tue Apr 12 10:32:41 BST 2011
The available options are -
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?
On Mon, Aug 22, 2011 at 6:38 PM, Ask Solem <ask at rabbitmq.com> wrote:
> On 22 Aug 2011, at 08:14, SiddharthSaha wrote:
> > I am using Celery with RabbitMQ. Lately, I have noticed that a large
> > number of temporary queues are getting made.
> > So, I experimented and found that when a task fails (that is a tasks
> > raises an Exception), then a temporary queue with a random name (like
> > c76861943b0a4f3aaa6a99a6db06952c) is formed and the queue remains.
> > Some properties of the temporary queue as found in rabbitmqadmin are
> > as follows -
> > auto_delete : True consumers : 0 durable : False messages : 1
> > messages_ready : 1
> > And one such temporary queue is made everytime a task fails (that is,
> > raises an Exception). How to avoid this situation? Because in my
> > production environment a large number of such queues get formed.
> > I do not want this temporary queue to be made. When a task fails, I
> > want that the task is tried one more time and even though it fails,
> > the temporary queue should not be made.
> > How can I do that?
> Please see
> If you want to disable states completely, set
> CELERY_RESULT_BACKEND = "disabled"
> If you want to automatically expire uncollected states, set
> Results are disabled by default in 2.3,
> see changelog:
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > rabbitmq-discuss at lists.rabbitmq.com
> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Content-Type: text/html; charset=ISO-8859-1
More information about the rabbitmq-discuss