As a developer I want to reevaluate worker issues to see if they have been resolved by moving from Celery3 to Celery4
Since Pulp2 has moved from Celery3.1 to Celery4.0  and Pulp3 is already using Celery4 we need to reevaluate celery related bugs and see which ones are still issues (and tag and fix them in Pulp3 if that is the case).
Here is a list of issues for memory leaks, cpu usage, and file descriptor leaks that might have been fixed by moving to Celery4:
#6 Updated by bmbouter over 2 years ago
- Status changed from NEW to CLOSED - WONTFIX
This is tagged as Pulp3 so I'm closing as WONTFIX because Pulp3 has moved to RQ. Learn more about the RQ transition with this blog post: https://pulpproject.org/2018/05/08/pulp3-moving-to-rq/
Please register to edit this issue