Project

Profile

Help

Task #3048

closed

Ensure that qpid connections aren't being affected by celery's forking mechanism

Added by daviddavis about 5 years ago. Updated over 3 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:
Pulp 2
Sprint:
Quarter:

Description

In issue #2979, we discovered that deadlocking sometimes occurred when a child process connects to mongodb due to the db connection being established before the fork. We need to ensure that something similar is not happening with our connection to qpid.

I would recommend that we first check the celery code as it might be already be closing/reopening the message broker connection after forking. I suspect it is since it would be a huge problem for celery and its users.

If not, we should probably reach out to qpid and see if it's ok to maintain a connection across a fork.


Related issues

Related to Pulp - Issue #2979: Celery workers may deadlock when PULP_MAX_TASKS_PER_CHILD is usedCLOSED - CURRENTRELEASEdaviddavisActions
Actions #1

Updated by daviddavis about 5 years ago

  • Related to Issue #2979: Celery workers may deadlock when PULP_MAX_TASKS_PER_CHILD is used added
Actions #2

Updated by daviddavis about 5 years ago

  • Subject changed from Ensure that qpid connections isn't being affected by celery's forking mechanism to Ensure that qpid connections aren't being affected by celery's forking mechanism
Actions #3

Updated by bmbouter over 3 years ago

  • Status changed from NEW to CLOSED - WONTFIX
Actions #4

Updated by bmbouter over 3 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF