Problem
No documentation exists for Meilisearch resource requirements in production/K8s deployments. Meilisearch auto-detects CPU count and spawns that many indexing threads, which can cause OOM on shared nodes.
Suggested additions
- Add resource requirement notes to deployment docs (minimum 2Gi RAM for Meilisearch)
- Document the
MEILI_MAX_INDEXING_THREADS env var (recommend setting to 2 for single-node clusters)
- Add to the K8s deployment manifests as a default
Problem
No documentation exists for Meilisearch resource requirements in production/K8s deployments. Meilisearch auto-detects CPU count and spawns that many indexing threads, which can cause OOM on shared nodes.
Suggested additions
MEILI_MAX_INDEXING_THREADSenv var (recommend setting to 2 for single-node clusters)