fix: raise Node heap cap to 512MB and bump pod memory limit #838
Reference in New Issue
Block a user
Delete Branch "bump-wgc-memory"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Dockerfile's
NODE_OPTIONS=--max-old-space-size=64was added to keep idle Node memory low, but in practice it OOMswgc router composeitself as soon as the supergraph has more than a handful of subgraphs:With an empty
cosmoRouterConfig, callers oflatestSchema(ref)get nothing — visible to the shiny gateway as it switches to consuming the pre-composed config straight from the schemas service.Changes
Dockerfile: bumpNODE_OPTIONS=--max-old-space-size64 → 512.k8s/deploy.yaml: bump container memory request 20Mi → 128Mi and add a 768Mi limit. The Dockerfile env covers the Node heap, so drop the manifest's NODE_OPTIONS override.The live
k8s.unbound.secluster was already patched in place viakubectl set env+kubectl set resources; this commit makes the manifest match (and removes the env override since the new image will carry the higher cap by default).Test plan
latestSchema(ref: "Shiny@prod")returns a non-emptycosmoRouterConfig.f3f96c59a1to921d4e39fa