for a non monolithic app, where should i declare the periodic tasks, and how?
yetship_ has quit
mihaj has quit
Dejan joined the channel
Dejan
I wonder did Celery guys intentionally decide to use celery celery-task-meta-<id> keys in Redis for all tasks. Why not have subkeys like... celery-task-meta:pending:<id> , celery-task-meta:started:<id> etc?
Since celery can't tell me what is waiting in the queue, I have to go through Redis keys to find this information
and I may have million keys...
euroaman007 joined the channel
euroaman007
woohoo what did i miss
?
spill the beans
Dejan
:)
nothing really...
it is mostly quiet here
euroaman007
too quiet
people working on celery too much
i am trolling to find some friends
lol
guru's on Celery
its kicking my butt
Dejan are u kicking ass and taking names
Dejan
nope
italorossi joined the channel
bakirelived
Dejan, that is celery 4?
i hust recently upgraded and saw on 4 release notes that some info of the task(like args and kwargs) was moved from payload to header to more easly spot that stuf maybe
Dejan
yea, that is a different story
what I was talking about is the inspection
as far as I know, you can't inspect tasks that are waiting in the queue
abhaykadam
hi, anyone have luck using celery with AMQP 1.0?
Dejan
nope
I only used Redis so far
and still do
euroaman007
redis all the way baby
i'll die if redis drys u[
up
Dejan
we can inspect active, scheduled, revoked, but how can i inspect what tasks are waiting in the queue to be picked?
clokep joined the channel
clokep has quit
clokep joined the channel
bakirelived
i never done with celery, only with a rabbit lib that tells me how many are in queue(and all of those are ready in my case)
__Yiota joined the channel
euroaman007 has quit
__Yiota joined the channel
wandering_vagran has quit
yetship_ joined the channel
yetship__ joined the channel
abhaykadam has quit
yetship_ has quit
subho joined the channel
malinoff has quit
__Yiota has quit
yetship joined the channel
wandering_vagran joined the channel
__Yiota joined the channel
yetship__ has quit
F2_ joined the channel
yetship has quit
bomb-on joined the channel
Deusdeorum has quit
subho has quit
bmbouter
abhaykadam: hey yes we can talk about amqp 1.0 and celery if you want here
I'm very familiar with this topic
and it's challenges...
wilo has quit
__Yiota has quit
Deusdeorum joined the channel
the_rat has quit
__Yiota joined the channel
wandering_vagran has quit
F2_ has quit
beardedeagle joined the channel
wandering_vagran joined the channel
__Yiota has quit
__Yiota joined the channel
__Yiota has quit
ccossentino joined the channel
eN_Satwik_Kolhe_ has quit
ogny has quit
beardedeagle joined the channel
beardedeagle
would it be posible to chain tasks together from .task()?
Basically I an trying to send_task from a flask app, then consume from a standalone celery app, but I have several tasks that I want to chain together in the celery app