Actions
Issue #8830
closedMemory leak in openapi.json schema generation.
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 112
Quarter:
Description
Ticket moved to GitHub: "pulp/pulpcore/2005":https://github.com/pulp/pulpcore/issues/2005
The issue was reproduced in the Automation Hub project.
Requests to openapi.json
schema cause uncontrolled growth of memory usage by gunicorn workers and eventually gunicorn worker being killed by OOMKiller.
Steps to reproduce:
Local test environment:
- Minikube instance.
- galaxy-api container configured with memory request\limit of 4 GiB of RAM
- 4 gunicorn workers
After ~1200 requests to openapi.json
gunicorn worker was killed due to OOM and restarted by gunicorn master process.
Updated by daviddavis over 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to fao89
- Triaged changed from No to Yes
- Sprint set to Sprint 97
Updated by pulpbot over 3 years ago
- Status changed from ASSIGNED to POST
Updated by ipanova@redhat.com over 3 years ago
- Sprint changed from Sprint 101 to Sprint 102
Updated by rchan about 3 years ago
- Sprint changed from Sprint 106 to Sprint 107
Updated by rchan about 3 years ago
- Sprint changed from Sprint 107 to Sprint 108
Updated by rchan about 3 years ago
- Sprint changed from Sprint 108 to Sprint 109
Updated by rchan about 3 years ago
- Sprint changed from Sprint 109 to Sprint 110
Updated by rchan about 3 years ago
- Sprint changed from Sprint 110 to Sprint 111
Updated by rchan almost 3 years ago
- Sprint changed from Sprint 111 to Sprint 112
Updated by pulpbot almost 3 years ago
- Description updated (diff)
- Status changed from POST to CLOSED - DUPLICATE
Actions