Project

Profile

Help

Issue #8830

Memory leak in openapi.json schema generation.

Added by osapryki 2 months ago. Updated 17 days ago.

Status:
POST
Priority:
Normal
Assignee:
Category:
-
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 101
Quarter:

Description

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.

History

#1 Updated by daviddavis 2 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to fao89
  • Triaged changed from No to Yes
  • Sprint set to Sprint 97

#2 Updated by pulpbot 2 months ago

  • Status changed from ASSIGNED to POST

#3 Updated by rchan 2 months ago

  • Sprint changed from Sprint 97 to Sprint 98

#4 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 98 to Sprint 99

#5 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 99 to Sprint 100

#6 Updated by rchan 17 days ago

  • Sprint changed from Sprint 100 to Sprint 101

Please register to edit this issue

Also available in: Atom PDF