DjangoBot: #celery

Is there some undocumented magic to unregister periodic tasks? I am just going through the getting started material and I registered a period task, but when I unregister it, it well..keeps on executing (despite it not being in the registry anymore)

Hi, I have used two Q (hi priority and low priority) on one host (via separate settings.py files), the question is -- can I use one celerybeat?

if yes, then how should look the celeribeat's settings.py?

as long as they use the same broker, sure

all celerybeat is doing is sending messages

so with all the periodic tasks installed, it sends messages when the tasks are scheduled

CELERY_QUEUES does not apply to celerybeat (except it provides the default queue settings for tasks when they're sent)

e.g. CELERY_DEFAULT_QUEUE

nikolay:

hello

i have a problem serializing django models

if I do model.save, task.delay(model)

and do another model.save in the task, it will report integrity error because it would use insert instead of update

trepca: I think you're supposed to pass around the primary key, so the task can get a fresh instance of the model object

I seem to remember reading that in th docs but can't find it now

There we go http://ask.github.com/celery/userguide/tasks.html

inline search for "gotcha"

padt: great, thanks!

if I have a task I want to execute on N workers (not just 1), how do I do that?

same task on a bunch of workers is done with fanout I think

I tried a fanout, but the task just gets picked up one one celeryd, seems like it round robins

Mkay. Then you'll have to check with asksol I guess

I hate bothering him all the time ;)

asksol: do you know how you can do one-to-many in celery then?

seems that binding 2 queues to the same exchange does the trick.

yeah, in topic exchanges that does the trick

two queues listening to the same routing key on the same exchange == fanout

so if you're using topic exchanges for that, it's the same, just a shortcut?

not sure what the plan is

it's a side effect I think :)

ask_sol - I think being able to specify a queue is probably the correct approach

I have a couple other small patches I need to send you, but I'm working from 1.0.0 and not from the git master branch

would you prefer I send them as patches, or check them in directly?