If Memory constraints passed to launcher use them to set max-old-space size for npm install #194
Labels
feature-request
New feature or request that needs to be turned into Epic/Story details
needs-triage
Needs looking at to decide what to do
Description
When starting a suspended instance that the user has been adding nodes to over time it may fail because npm consumes more memory than the container allows (k8s/docker)
On these platforms we are now passing the memory/cpu limits to the nr-launcher as a env var, we should be able to use this to set the NODE_OPTIONS env var for the npm process to limit the memory used. This should stop npm getting killed by the container manager.
The text was updated successfully, but these errors were encountered: