v2.6.1
Release date: September 3, 2025
| Milvus Version | Python SDK Version | Node.js SDK Version | Java SDK Version | Go SDK Version |
|---|---|---|---|---|
| 2.6.1 | 2.6.1 | 2.6.0 | 2.6.3 | 2.6.1 |
We are excited to announce the release of Milvus 2.6.1! This version builds upon the major architectural advancements of previous releases, delivering critical enhancements focused on production stability, performance, and operational robustness. This release addresses key community feedback and strengthens the system for large-scale deployments. We strongly encourage all users to upgrade to benefit from a more stable, performant, and reliable system.
Improvements
- Supports POSIX-compatible file systems for remote storage (#43944)
- Introduces model-based rerankers (#43270)
- Optimizes the performance of comparison expressions on primary key fields (#43154)
- Collects doc_id from posting list directly to accelerate text match (#43899)
- Optimizes query performance by converting multiple != conditions into a single NOT IN clause (#43690)
- Enhances resource management for the caching layer during segment loading (#43846)
- Improves memory estimation for interim indexes during data loading (#44104)
- Makes the build ratio for interim indexes configurable (#43939)
- Adds a configurable write rate limit to the disk writer (#43912)
- SegCore parameters can now be updated dynamically without restarting the Milvus service (#43231)
- Adds unified gRPC latency metrics for better observability (#44089)
- Includes client request timestamps in gRPC headers to simplify debugging (#44059)
- Supports trace log level for segcore (#44003)
- Adds a configurable switch to adjust consistency guarantees for higher availability (#43874)
- Implements a robust rewatch mechanism to handle etcd connection failures (#43829)
- Improves the internal node health check logic (#43768)
- Optimizes metadata access when listing collections (#43902)
- Upgrades the Pulsar client to v0.15.1 official version and adds more logging (#43913)
- Upgrades aws-sdk from 1.9.234 to 1.11.352 (#43916)
- Supports dynamic interval updates for ticker components (#43865)
- Improves auto-detection of ARM SVE instruction sets for bitset operations (#43833)
- Improves the error message when a text or phrase match fails (#43366)
- Improves the error message for vector dimension mismatches (#43835)
- Improves error reporting for append timeouts when the object store is unavailable (#43926)
Bug fixes
- Fixes a potential Out-Of-Memory (OOM) issue during Parquet file imports (#43756)
- Fixes an issue where standby nodes could not recover if their lease expired (#44112)
- Handles compaction retry state correctly (#44119)
- Fixes a potential deadlock between continuous read requests and index loading that could prevent index loading (#43937)
- Fixes a bug that could cause data deletions to fail in high-concurrency scenarios (#43831)
- Fixes a potential race condition when loading text and JSON indexes (#43811)
- Fixes a node status inconsistency that could occur after a QueryCoord restart (#43941)
- Ensures that a "dirty" QueryNode is properly cleaned up after a restart (#43909)
- Fixes an issue where the retry state was not handled correctly for requests with non-empty payloads (#44068)
- Fixes an issue where the bulk writer v2 did not use the correct bucket name (#44083)
- Enhances security by hiding sensitive items from the RESTful get_configs endpoint (#44057)
- Ensures that object uploads for woodpecker are idempotent during timeout retries (#43947)
- Disallows importing null elements in array fields from Parquet files (#43964)
- Fixes a bug where the proxy cache was not invalidated after creating a collection alias (#43854)
- Improves the internal service discovery mechanism for streaming nodes (#44033)
- Fixes resource group logic to correctly filter streaming nodes (#43984)
- Adds the databaseName label to metrics to prevent naming conflicts in multi-database environments (#43808)
- Fixes a logic error in internal task state handling (#43777)
- Optimizes the initialization timing of the internal metrics to avoid potential panic (#43773)
- Fixes a rare potential crash in the internal HTTP server (#43799)