Actions
Story #2632
closed
As a developer I want to reevaluate worker issues to see if they have been resolved by moving from Celery3 to Celery4
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Since Pulp2 has moved from Celery3.1 to Celery4.0 [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:
Related issues
Updated by bizhang about 7 years ago
- Related to Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restart added
Updated by bizhang about 7 years ago
- Related to Issue #1330: celery worker memory leak and high CPU after restarting qpidd many times added
Updated by bizhang about 7 years ago
- Related to Issue #2492: Small memory leak in httpd when dispatching Pulp tasks added
Updated by bizhang about 7 years ago
- Related to Issue #1967: Duplicate instances of pulp_celerybeat on the same host will cause some tasks to be dispatched multiple times added
Updated by bizhang about 7 years ago
- Related to Issue #1779: Repo Copy Memory Usage added
Updated by bmbouter almost 6 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/
Actions
.