LoginSign Up
← Back to all sparks
M

Meilisearch

DEVOPS
Velocity5.0

Open-source, fast, typo-tolerant search engine API.

www.meilisearch.com ↗

Meilisearch tightens sharding latency and index authorization in a flurry of maintenance releases.

searchshardingperformanceopen-sourcedevtoolssecurity
◆Current state
Meilisearch is deep in active maintenance, shipping bug-fix point releases and a series of prototype branches targeting sharding performance. The v1.53.x line addresses search-result correctness (stop-word highlighting, exactness ranking edge cases) and a security hardening fix tying authorization checks to index opening. Alongside stable releases, the reuse-http-client prototype branch is testing a ~100ms-per-request latency reduction for users running clustered setups.
◆Where it's heading
The team is working two tracks simultaneously: quality stabilization on the stable line and infrastructure-level optimizations on prototype branches for sharding. The addition of MEILI_EXPERIMENTAL_TASK_QUEUE_MAX_READERS suggests increasing attention to LMDB resource limits under high concurrent load—a pattern pointing toward larger deployments. Expect the HTTP client reuse optimization to land in a stable minor once the prototype cycle closes.
◆Prediction
The next stable release will likely absorb the reuse-http-client prototype changes, delivering measurable latency improvement for multi-node deployments. If the crash-fix branch work uncovered a systemic allocator issue (mimalloc swap), expect a follow-on patch for stability.

◆Recent moves

  1. 8d ago

    v1.53.2: security fix + correctness patches

    v1.53.2 bundles three correctness fixes—stop-word highlighting, exactness ranking after settings changes, and 100ms task-replication penalty removal—plus a security fix tying authorization to index opening. Small on the surface, but the authorization fix closes a potential access-control gap in multi-index setups.

    View source ↗
  2. 13d ago

    prototype-v1.50.0-reuse-http-client.3

    Internal prototype iteration adding error context to CorruptedTaskQueue messages. No user-visible change; part of the reuse-http-client experiment cycle.

    View source ↗
  3. 13d ago

    prototype-v1.50.0-reuse-http-client.2

    Another iteration of the reuse-http-client prototype branch with the same error-context change. Pure internal scaffolding; no shipped feature.

    View source ↗
  4. 13d ago

    Allow deleting non-deserializable enqueued tasks

    Adds the ability to delete enqueued tasks that can't be deserialized, preventing a stuck-queue scenario. A reliability guard that operators running long-lived Meilisearch instances will notice if they've ever hit a corrupted task edge case.

    View source ↗
  5. 14d ago

    Prototype: reuse HTTP client for sharding, saves ~100ms per proxied task

    The reuse-http-client.0 prototype demonstrates ~100ms latency reduction per proxied task in sharded deployments by keeping the index-scheduler web client alive across requests. This fits the pattern of Meilisearch investing in clustered-scale performance ahead of a likely stable release.

    View source ↗
  6. 22d ago

    prototype-v1.52.3-fix-crashes.6

    Swaps mimalloc to a temporary repository during the crash-fix prototype cycle—an internal dependency management change with no user-visible effect.

    View source ↗