Project

Profile

Help

Issue #9253

closed

sync task uses too many DB connections

Added by dkliban@redhat.com over 3 years ago. Updated about 3 years ago.

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

Description

Django 3.2 opens up new DB connection for each coroutine, unless the call is wrapped with sync_to_async.


Related issues

Related to Pulp - Issue #9129: Syncing is running out of DB connectionsCLOSED - CURRENTRELEASEgerrodActions
Copied from File Support - Task #9252: sync task uses too many DB connectionsCLOSED - CURRENTRELEASE

Actions
Actions #1

Updated by dkliban@redhat.com over 3 years ago

  • Copied from Task #9252: sync task uses too many DB connections added
Actions #2

Updated by dkliban@redhat.com over 3 years ago

  • Related to Issue #9129: Syncing is running out of DB connections added
Actions #3

Updated by pulpbot over 3 years ago

  • Status changed from NEW to POST
Actions #4

Updated by dalley over 3 years ago

  • Assignee set to dkliban@redhat.com
  • Triaged changed from No to Yes
  • Sprint set to Sprint 103

Added by dkliban@redhat.com over 3 years ago

Revision 9d10803f | View on GitHub

Runs all DB queries synchronously during a sync task.

Required PR: https://github.com/pulp/pulpcore/pull/1553

closes: #9253

Actions #5

Updated by dkliban@redhat.com over 3 years ago

  • Status changed from POST to MODIFIED
Actions #6

Updated by dalley about 3 years ago

  • Sprint/Milestone set to 3.15.0
Actions #7

Updated by pulpbot about 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF