Page MenuHomePhabricator

Investigate potential memory leak
Closed, ResolvedPublicSpike

Description

What:
We have observed signs of potential memory leak in the Orchestrator. We need to investigate to try and confirm if a leak indeed exists. If so, identify root causes and next steps for mitigation.

Why:

  • memory usage increase over time and has ended frequently in service restarts or OOM kills in Prod logs
  • performance struggles with response delays seemingly correlated with uptime in user experience

Details

Related Changes in Gerrit:
Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
make sure that heap logs have req-id'srepos/abstract-wiki/wikifunctions/function-orchestrator!466ecarggrace/T406926/add-request-ids-to-heap-logsmain
Customize query in GitLab

Event Timeline

Restricted Application changed the subtype of this task from "Task" to "Spike". · View Herald TranscriptOct 9 2025, 8:36 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
ecarg changed the task status from Open to In Progress.Oct 9 2025, 8:37 PM
ecarg triaged this task as High priority.

Change #1196439 had a related patch set uploaded (by Jforrester; author: Jforrester):

[operations/deployment-charts@master] wikifunctions: Upgrade orchestrator from 2025-10-06-225918 to 2025-10-14-194525

https://gerrit.wikimedia.org/r/1196439

Change #1196439 merged by jenkins-bot:

[operations/deployment-charts@master] wikifunctions: Upgrade orchestrator from 2025-10-06-225918 to 2025-10-14-194525

https://gerrit.wikimedia.org/r/1196439

Change #1198036 had a related patch set uploaded (by Cory Massaro; author: Cory Massaro):

[operations/deployment-charts@master] Wikifunctions: Upgrade orchestrator from 2025-10-14-194525 to 2025-10-22-011302.

https://gerrit.wikimedia.org/r/1198036

Change #1198036 merged by jenkins-bot:

[operations/deployment-charts@master] Wikifunctions: Upgrade orchestrator from 2025-10-14-194525 to 2025-10-22-011302.

https://gerrit.wikimedia.org/r/1198036

Have not found clear evidence of memory leakage, I am resolving this hypothesis so that I can move on to others

reopening as per COW investigation on Orchestrator OOM's today

Jdforrester-WMF changed the task status from Open to In Progress.Nov 20 2025, 8:53 PM

Memory leaks detected this quarter and created tools to track Node garbage collection and memory usage using Docker stats.