Project

Profile

Help

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

Added by bizhang almost 6 years ago. Updated almost 4 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
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:

[0] https://pulp.plan.io/issues/2527


Related issues

Related to Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restartCLOSED - CURRENTRELEASEActions
Related to Pulp - Issue #1330: celery worker memory leak and high CPU after restarting qpidd many timesCLOSED - WONTFIXActions
Related to Pulp - Issue #2492: Small memory leak in httpd when dispatching Pulp tasksCLOSED - WONTFIXActions
Related to Pulp - Issue #1967: Duplicate instances of pulp_celerybeat on the same host will cause some tasks to be dispatched multiple timesCLOSED - WONTFIXActions
Related to Pulp - Issue #1779: Repo Copy Memory UsageCLOSED - WONTFIXActions

Also available in: Atom PDF