-
Notifications
You must be signed in to change notification settings - Fork 12
Celery redbeat
scheduler compatability
#20
Comments
I can't reproduce this exception. Can you create minimal project with single void task, where this problem will be reproduced? |
I corrected python's version for this problem as 3.8 in my issue description. I'll share small project with a single task soon. Thanks for your quick reply. |
@kai3341 I've rechecked my code and fond that celery_poop_asyncio is working as expected. and here is Working example of it. However, What I have observed is that this code is not compatible to work with redbeat scheduler. For the obvious reasons, we should have the capabilities to edit, remove the task in runtime. As redbeat provides those capabilities. By any chance, are you planning to work on such features, or we would need to get in touch with @sibson to update redbeat source code to make it compatible with the coroutine task? Meanwhile, I just wanted to express my thanks for the great work you guys have done for the community. |
@codesutras i think i'll solve this problem |
redbeat
scheduler compatability
Perfect... Thanks a lot for taking it up. |
this will be a great thing! |
ohho |
@kai3341 Can I offer a bounty for this? |
It might be a hack, but I got it to work dirty by creating this file and using this class as a scheduler:
|
@zikphil great job! Almost ok -- redis IO-bound operations most be wrapped to async/await via |
@zikphil @codesutras please check #28 |
Description
Getting below exception while starting celery beat with --scheduler celery_pool_asyncio:PersistentScheduler and it's not sending task to worker.
Celery beat should start normally and it should send task to workers.
What I Did
I executed below command and got exception.
celery beat -A my.app --scheduler celery_pool_asyncio:PersistentScheduler
The text was updated successfully, but these errors were encountered: