You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 5, 2023. It is now read-only.
Can we send the SIGUSR1 signal to the pyres_manager and have it dump the current log traceback of workers?
kill -USR1 <pid of pyres_manager>
dump the current traceback to -f pyres.log
This feature is really useful because often there are workers that might get stuck on a memcache connection or some sort of service that is hung due to high CPU usage etc. Celery supports this feature and it would be good to have this in pyres as well.
The text was updated successfully, but these errors were encountered:
Can we send the SIGUSR1 signal to the pyres_manager and have it dump the current log traceback of workers?
dump the current traceback to -f pyres.log
This feature is really useful because often there are workers that might get stuck on a memcache connection or some sort of service that is hung due to high CPU usage etc. Celery supports this feature and it would be good to have this in pyres as well.
The text was updated successfully, but these errors were encountered: