-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--autoreload not working since 3.1, change to non-blocking inotify needed #1658
Comments
I tested and it works but the pool takes some time to catch up (each process in the pool must process one task before they are restarted). The reload does not work if you change code in a task, but that is a limitation in the python reload function it seems. |
To fix the pool lag it should write one "noop" task to each process in the pool when a file changes, that way the processes will wake up from its waiting for I/O state. |
Can confirm if the code in a task is changed, it takes one task to be processed after the change has been made before the change takes effect. |
@ask can you help with as you said: "To fix the pool lag it should write one "noop" task to each process in the pool". |
Since the celery auto-reload feature which it enables hasn't been working for some time regardless: celery/celery#1658 celery/celery#1025 celery/celery#1880
Since the celery auto-reload feature which it enables hasn't been working for some time regardless: celery/celery#1658 celery/celery#1025 celery/celery#1880
Closing this, as we don't have the resources to complete this task. We will remove the docs for --autoreload and --autoscale in 4.0 (it will still be there, but no documented) |
At least put a note in the docs saying |
I put that in my todo list like a year ago. Currently I'm hard at work on Celery 4 which is nearly complete, and the option will be invisible, and undocumented in master very soon. |
bump :)
|
The option is ignored because of the changes in autoreload.py from this in 3.0
to the current code.
According to Ask, if we want this option available again, a patch is needed for:
The text was updated successfully, but these errors were encountered: