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
I have checked the issues list
for similar or identical feature requests.
I have checked the pull requests list
for existing proposed implementations of this feature.
I have checked the commit log
to find out if the same feature was already implemented in the
main branch.
I have included all related issues and possible duplicate issues
in this issue (If there are none, check this box anyway).
Related Issues and Possible Duplicates
Related Issues
None
Possible Duplicates
None
Brief Summary
When I started using the parameters --max-tasks-per-child and --max-memory-per-child, I first tried with --max-tasks-per-child=3 to see if it was working.
I was starring at the logs and I had no clue if it was working or not, except by checking the INFO/ForkPoolWorker-... worker number to see it was changing every 3 tasks. It's ok for three but could be annoying to check with greater limit.
I didn't test --max-memory-per-child yet to see if it was in the logs but I guess not.
Would it be possible to add a log for that ?
Something like :
logger.info("Stopped worker-<number_of_the_worker>: reached max tasks limit
logger.info("Stopped worker-<number_of_the_worker>: reached max memory limit
Small note/context :
I'm currently using celery==5.2.7 and django-celery-beat==2.5.0 and I want to to start using these options because once every a few days, I have to restart my application as my celery workers seem to reach some kind of memory limit. And I'd like to have these worker events (drop worker,...) in my logs.
I'm open to make the contribution myself if I can find the place where such check is done (in billiard apparently).
Design
Architectural Considerations
None
Proposed Behavior
Something like :
logger.info("Stopped worker-<number_of_the_worker>: reached max tasks limit
logger.info("Stopped worker-<number_of_the_worker>: reached max memory limit
Proposed UI/UX
N/A
Diagrams
N/A
Alternatives
None
The text was updated successfully, but these errors were encountered:
Checklist
for similar or identical feature requests.
for existing proposed implementations of this feature.
to find out if the same feature was already implemented in the
main branch.
in this issue (If there are none, check this box anyway).
Related Issues and Possible Duplicates
Related Issues
Possible Duplicates
Brief Summary
When I started using the parameters
--max-tasks-per-child
and--max-memory-per-child
, I first tried with--max-tasks-per-child=3
to see if it was working.I was starring at the logs and I had no clue if it was working or not, except by checking the
INFO/ForkPoolWorker-...
worker number to see it was changing every 3 tasks. It's ok for three but could be annoying to check with greater limit.I didn't test
--max-memory-per-child
yet to see if it was in the logs but I guess not.Would it be possible to add a log for that ?
Something like :
logger.info("Stopped worker-<number_of_the_worker>: reached max tasks limit
logger.info("Stopped worker-<number_of_the_worker>: reached max memory limit
Small note/context :
I'm currently using
celery==5.2.7
anddjango-celery-beat==2.5.0
and I want to to start using these options because once every a few days, I have to restart my application as my celery workers seem to reach some kind of memory limit. And I'd like to have these worker events (drop worker,...) in my logs.I'm open to make the contribution myself if I can find the place where such check is done (in
billiard
apparently).Design
Architectural Considerations
None
Proposed Behavior
Something like :
logger.info("Stopped worker-<number_of_the_worker>: reached max tasks limit
logger.info("Stopped worker-<number_of_the_worker>: reached max memory limit
Proposed UI/UX
N/A
Diagrams
N/A
Alternatives
None
The text was updated successfully, but these errors were encountered: