MeilisearchKubernetes

Meilisearch OOM kill during indexing operations

critical
Resource ContentionUpdated Feb 13, 2025(via Exa)
How to detect:

Meilisearch process terminated by OOM killer during indexing operations, particularly in v1.13.x. Memory usage spikes from baseline 50% to 70%+ during indexing, eventually consuming all available RAM despite max_indexing_memory configuration. Process exits with code=killed, status=9/KILL.

Recommended action:

Enable --experimental-reduce-indexing-memory-usage flag to significantly reduce memory consumption during indexing. Optionally reduce --max-indexing-threads to 1 to further constrain memory usage. Monitor memory allocation using --log-level DEBUG at start of indexing operations to verify 'Total BBQueue size' and 'Total extractor memory' values.