Meilisearch
Open-source, fast, typo-tolerant search engine API.
Meilisearch is trimming ~100ms sharding latency in prototype while shipping task-queue controls in stable.
◆Recent moves
- 5d ago
prototype-v1.50.0-reuse-http-client.3
Adds diagnostic context to the CorruptedTaskQueue error message in the HTTP client reuse prototype — a debugging aid for operators hitting corrupted state, with no user-visible behavior change.
View source ↗ - 5d ago
Add error context for CorruptedTaskQueue in HTTP client reuse prototype
Second iteration of the CorruptedTaskQueue error context fix in the reuse-http-client prototype — iterative debugging improvement with no functional change.
View source ↗ - 5d ago
Allow deletion of non-deserializable enqueued tasks
Allows operators to delete enqueued tasks that cannot be deserialized — a practical fix for sharded deployments where corrupted or schema-mismatched tasks could block the queue indefinitely.
View source ↗ - 6d ago
Prototype: reuse HTTP client when proxying tasks (~100ms savings for sharded deployments)
Prototype release that reuses the index-scheduler's HTTP client when proxying tasks in sharded setups, saving approximately 100ms per proxied task. This fits the trajectory of sharding becoming a production-grade, tunable deployment mode rather than an experimental one.
View source ↗ - 14d ago
prototype-v1.52.3-fix-crashes.6
Switches to a temporary mimalloc repository in the crash-fix prototype branch — a build dependency swap with no user-facing impact.
View source ↗ - 26d ago
🖇️ v1.53.1
v1.53.1 ships MEILI_EXPERIMENTAL_TASK_QUEUE_MAX_READERS, an environment variable giving operators direct control over the number of simultaneous LMDB read transactions on the task queue. This is the kind of operational knob that matters at scale — pairing with the sharding prototype work underway, it continues the trend of exposing concurrency controls to operators rather than baking them as fixed constants.
View source ↗