#celery

moodh: you coud use custom routing

and do fanout

hello All

I need little help with my celery 3.0.15 setup

moodh: set up a broadcast queue

I am using celery scheduler to setup tasks. The scheduler adds task at correct time ...

but workers seem to pick the last after few hours ...

I have put up details on http://stackoverflow.com/questions/22105976/cel...

asksol: got any docs for this?

moodh: user guide -> Routing I believe

Cool, i'll look into it =)

asksol: broadcasting would send me 1 task per worker, is it possible to send 1 task per server? or do i need to do some kind of lock on each server?

moodh: not sure what the difference would become?

?

s/become/be

stupid autocorrect

multiple workers on each server, but i figured out another approach =)

thanks anyway!

kombu 3.0.13 is on PyPI

asksol: how should I handle an authentication exception if the supplied username and password don't authenticate?

currently

I see that I can set attributes on the transport object

bmbouter: there's no specific practice for that, probably want an error that is not in connection_errors

as that is not recoverable

are the different error classes documented somewhere? I now know about connection_errors and that it is not recoverable, but are there other error classes?

previously there was connection_errors and channel_errors

for recoverable connection and channel errors

so which are recoverable and which are not recoverable?

now there is recoverable_connection_errors, recoverable_channel_errors that can be defined in which case it will not close the connection if there is a channel error

oh I see

not recoverable errors aren't handled

ok great thanks

amqp itself does have a concept of recoverable/irrecoverable but kombu only uses recoverable status

pyamqp itself

ok cool

so I figured out the error that I was working on last week

asksol: should I not tell celery about unrecoverable connection errors and just let them be raised up the stack?