You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
install.py should recommend different settings for minimal memory instances, if possible #483
When following the default recommendation of the memory allocation the setup script provides and the system has no swap configured Opensearch repeatedly crashed because it can't allocate enough memory. Problems occured when the server has below 12 GB memory and now swap configured, it happend on Ubuntu, Debian and OpenSUSE.
To reproduce
Steps to reproduce the behavior:
Server with 8GB memory and no swap
Install according to documentation
Start Malcolm with the script
Expected behavior
The script should recommend less memory for Opensearch and Logstash when the system has below 12 GB memory and no swap.
Any helpful log output or screenshots
The following output is shown (not exactly copied)
Can probably investigate this as part of the installer overhaul. Should be pretty simple to integrate given how modular the new ConfigItem approach is.
After looking at this again (and at #1188, which tried lowering the OpenSearch and Logstash heap defaults below 12 GB), I don't think smaller heaps are the right fix. Malcolm's full stack doesn't run reliably on a host this small no matter how the heaps are split. Lowering them mostly turns an obvious failure (OpenSearch exiting with code 137) into an unstable system that's harder to diagnose.
I think a better plan is to handle this in the installer:
Detect when the host has less memory than Malcolm's documented minimum (and possibly detect and flag it more strongly when no swap is configured)
Warn clearly before any configuration is written that the system is undersized and services are likely to be killed or unstable.
Possibly point out which optional services (NetBox, file extraction and scanning, etc.) could be disabled for a test or evaluation system, while being clear that it isn't a supported configuration.
Activity
jjrush commentedon Oct 18, 2025
Can probably investigate this as part of the installer overhaul. Should be pretty simple to integrate given how modular the new ConfigItem approach is.
Reduce defaults for low-memory installations
Reduce defaults for low-memory installations
mmguero commentedon Oct 12, 2026
After looking at this again (and at #1188, which tried lowering the OpenSearch and Logstash heap defaults below 12 GB), I don't think smaller heaps are the right fix. Malcolm's full stack doesn't run reliably on a host this small no matter how the heaps are split. Lowering them mostly turns an obvious failure (OpenSearch exiting with code 137) into an unstable system that's harder to diagnose.
I think a better plan is to handle this in the installer:
Leaving this open to track that work.