-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install nodes that require significant memory #626
Comments
Purely from a user perspective it feels like whats needed here is the ability to 'burst' memory usage above the baseline, I'm not sure if there's anything in k8s that would allow for that? |
I've converted this to a story as I'm not sure its really a bug as much as a limitation of the current platform |
This came up today for a FF Cloud customer. They can't get node-red-contrib-chatbot to install on a small instance but it does work on medium. I suspect the only resource which is causing that problem is RAM. |
Currently, when npm is killed as part of startup, we don't communicate well tot he user why this failed. We're seing this issue a lot, we have two methods for resolving:
(1) is the quick MVP here, and (2) should be a longer term objective. |
Some nodes in the Node-RED ecosystem have a larger install-time memory requirement than others. This can lead to installs failing when running in a Stack with a limited memory footprint.
For example, the 256 memory limit we have in FFCloud is fine for most cases, but will fail for a module like
node-red-contrib-graphql-server
.This issue is to track how we can improve the user experience around this scenario
Node-RED
npm
, node-red doesn't capture the full log output. That can make it hard to know why an install failed. Capturing the full log could produce a lot of noise. It would be interesting to see if the exit code of a killed process is distinct enough for Node-RED to detect and log appropriatelyFlowForge
Tasks
The text was updated successfully, but these errors were encountered: