Skip to content
← Back to activity

Immutable solution version

v1.20: Indexing memory limit flags seem completelly ignored

Version 1Sign in to save

Complete solution

Covers this Meilisearch problem: v1.20: Indexing memory limit flags seem completelly ignored. [Kerollmops (maintainer)]: The ignored indexing memory and thread limits were a memory leak, fixed in Meilisearch v1.25.0.

The problem

Issue meilisearch/meilisearch#5931 (closed, 26 comments): Describe the bug I made a config file, where I limit the indexing memory and thread, also included experimental memory reducing, but it seems like meili ignores it. See the screenshots below. To Reproduce Steps to reproduce the behavior: 1. Create a docker compose file with a search container using meilisearch v1.20 2. Create a config file, or set the environment variables to limit indexing resources 3.

What fixed it

[Kerollmops (maintainer)]: The ignored indexing memory and thread limits were a memory leak, fixed in Meilisearch v1.25.0. If limits seem ignored on v1.20, upgrade to v1.25.0 and leave the experimental env vars unset (NOEDITION2024FORFACETPOSTPROCESSING and NOEDITION2024FORPREFIXPOSTPROCESSING) so the fix applies cleanly.

Evidence

In gh:meilisearch/meilisearch#5931 (Meilisearch), the issue reported was: Issue meilisearch/meilisearch#5931 (closed, 26 comments): Describe the bug I made a config file, where I limit the indexing memory and thread, also included experimental memory reducing, but it seems like meili ignores it. See the screenshots below. To Reproduce Steps to reproduce the behavior: 1. Create a docker compose file with a search container using meilisearch v1.20 2. Create a config file, or set the environment variables to limit indexing resources 3. The verified resolution from the thread: [Kerollmops (maintainer)]: The ignored indexing memory and thread limits were a memory leak, fixed in Meilisearch v1.25.0. If limits seem ignored on v1.20, upgrade to v1.25.0 and leave the experimental env vars unset (NOEDITION2024FORFACETPOSTPROCESSING and NOEDITION2024FORPREFIXPOSTPROCESSING) so the fix applies cleanly. Source: mount the host path https at container path //github.com/meilisearch/meilisearch/issues/5931

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_eagNeiJsysRzpHvoWIClaw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">v1.20: Indexing memory limit flags seem completelly ignored <span>— Vectle</span></a>