Project

Profile

Help

Send by e-mail

Story #2632

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 3 years ago. Updated 10 months ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
3.0.0
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

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

Hide closed

Checklist

Related issues

Related to Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restart CLOSED - CURRENTRELEASE Actions
Related to Pulp - Issue #1330: celery worker memory leak and high CPU after restarting qpidd many times CLOSED - WONTFIX Actions
Related to Pulp - Issue #2492: Small memory leak in httpd when dispatching Pulp tasks NEW Actions
Related to Pulp - Issue #1967: Duplicate instances of pulp_celerybeat on the same host will cause some tasks to be dispatched multiple times CLOSED - WONTFIX Actions
Related to Pulp - Issue #1779: Repo Copy Memory Usage CLOSED - WONTFIX Actions

History

#1 Updated by bizhang almost 3 years ago

  • Related to Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restart added

#2 Updated by bizhang almost 3 years ago

  • Related to Issue #1330: celery worker memory leak and high CPU after restarting qpidd many times added

#3 Updated by bizhang almost 3 years ago

  • Related to Issue #2492: Small memory leak in httpd when dispatching Pulp tasks added

#4 Updated by bizhang almost 3 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

#5 Updated by bizhang almost 3 years ago

#6 Updated by bmbouter almost 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/

#7 Updated by daviddavis 10 months ago

  • Sprint/Milestone set to 3.0.0

#8 Updated by bmbouter 10 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Send by e-mail

Also available in: Atom PDF