Technologies/Meilisearch/meilisearch.index.is_indexing
MeilisearchMeilisearchMetric

meilisearch.index.is_indexing

Whether index is processing
Dimensions:None
Available on:Native (1)
Interface Metrics (1)
Native
Whether the index is currently processing documents
Dimensions:None
Sources
index.is_indexingwww.meilisearch.com

Technical Annotations (37)

Configuration Parameters (7)
max_payload_sizerecommended: 100MB (default, can be increased)
Maximum size for batch document uploads
max_indexing_threadsrecommended: 2
limit concurrent indexing to prevent resource exhaustion on large indexes
max_indexing_memoryrecommended: 4 GiB
cap memory usage during indexing to prevent system-wide resource contention
--max-indexing-memoryrecommended: Set to half of desired maximum memory allocation to account for 2x spike
Controls memory budget for indexing but actual usage can reach 2x this value during settings updates
--experimental-reduce-indexing-memory-usagerecommended: enabled
Significantly reduces memory consumption during indexing operations
--max-indexing-threadsrecommended: 1
Reducing thread count can help constrain memory usage
--log-levelrecommended: DEBUG
Enables logging of memory allocation metrics at indexing start
Error Signatures (5)
408http status
Request Timeouthttp status
too many open fileserror code
meilisearch.service: Failed with result 'oom-kill'log pattern
Main process exited, code=killed, status=9/KILLexit code
CLI Commands (2)
--experimental-reduce-indexing-memory-usageremediation
--log-level DEBUGdiagnostic
Technical References (23)
actix-webcomponentseparatorconceptproximityconcept#3866componentgrenadcomponentextractorcomponentLMDBcomponentwrite transactionconceptfallocate(2)componentsettingsUpdatecomponentTransformcomponentIndexDocumentscomponentSettings::reindexcomponentfilterable attributesconceptwords_prefix_integer_docidscomponentsearchable attributesconceptBBQueuecomponentextractor memorycomponentBBQueue sizecomponentindexing threadconcept/statscomponentauto-batchingconceptbatch indexingconcept
Related Insights (15)
HTTP 408 timeout errors during concurrent indexing and querieswarning
▸
High-density punctuation without spaces causes indexing slowdownwarning
▸
Crashes during document indexation due to memory exhaustioncritical
▸
High percentage of searches return no resultswarning
▸
Unconfigured indexing resource limits cause periodic service hangs with large indexescritical
▸
Too many open files error during indexingcritical
▸
Single-threaded bottleneck limits high-core machine performancewarning
▸
Filesystem cache pressure from temporary file proliferationwarning
▸
Index settings update causes infinite OOM loopcritical
▸
Settings update allocates twice the max-indexing-memory limitwarning
▸
LMDB database writes cause memory spikes beyond configured limitswarning
▸
Meilisearch OOM kill during indexing operationscritical
▸
max_indexing_memory parameter uses only 10% for indexing with 150MB minimum per threadwarning
▸
Small batch indexing causes prolonged high CPU usagewarning
▸
Large batch document indexing monopolizes workers causing HTTP 408warning
▸