Project

Profile

Help

Issue #1655

closed

pulp task workers connect to mongo before forking

Added by semyers about 8 years ago. Updated almost 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

When celery task workers start up, the connect to mongo before forking off the process that actually works tasks. I've isolated the current known locations where the forked workers connect to mongo and wrapped them with a context manager to suppress them[0], but the initial connection(s) that happen(s) before the worker is still not found.

My debugging method used to find the post-fork connections was to rpdb.set_trace() immediately after pymongo raises the connect before fork warning; a similar method may be helpful in finding connections created pre-fork.

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


Related issues

Related to Pulp - Issue #1580: Cannot Download Published RPMsCLOSED - CURRENTRELEASEsemyersActions
Actions #1

Updated by semyers about 8 years ago

  • Related to Issue #1580: Cannot Download Published RPMs added
Actions #2

Updated by bmbouter about 8 years ago

  • Priority changed from Low to Normal
  • Triaged changed from No to Yes
Actions #4

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added
Actions #5

Updated by dkliban@redhat.com almost 5 years ago

  • Status changed from NEW to CLOSED - WONTFIX

This is not going to be fixed for pulp 2. Pulp 3 does not rely on Mongo.

Also available in: Atom PDF