Actions
Issue #9253
closedsync task uses too many DB connections
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
Updated by dkliban@redhat.com over 3 years ago
- Copied from Task #9252: sync task uses too many DB connections added
Updated by dkliban@redhat.com over 3 years ago
- Related to Issue #9129: Syncing is running out of DB connections added
Updated by pulpbot over 3 years ago
- Status changed from NEW to POST
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
Updated by dkliban@redhat.com over 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset 9d10803fc558459cf8f8e1086d689b4ccfaf98ac.
Updated by pulpbot about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Runs all DB queries synchronously during a sync task.
Required PR: https://github.com/pulp/pulpcore/pull/1553
closes: #9253