v2.2.6
Release date: 18 April, 2023
| Milvus version | Python SDK version | Java SDK version | Go SDK version | Node.js SDK version |
|---|---|---|---|---|
| 2.2.6 | 2.2.7 | 2.2.5 | 2.2.1 | 2.2.4 |
Upgrade to Milvus 2.2.6 as soon as possible!
You are advised to refrain from using version 2.2.5 due to several critical issues that require immediate attention. Version 2.2.6 addresses these issues. One of the critical issues is the inability to recycle dirty binlog data. We highly recommend using version 2.2.6 version instead of version 2.2.5 to avoid any potential complications.
If you hit the issue where data on object storage cannot be recycled, upgrade your Milvus to v2.2.6 to fix these issues.
Bugfix
- Fixed the problem of DataCoord GC failure (#23298)
- Fixed the problem that index parameters passed when creating a collection will override those passed in subsequent create_index operations (#23242)
- Fix the problem that the message backlog occurs in RootCoord, which causes the delay of the whole system to increase (#23267)
- Fixed the accuracy of metric RootCoordInsertChannelTimeTick (#23284)
- Fixed the issue that the timestamp reported by the proxy may stop in some cases (#23291)
- Fixed the problem that the coordinator role may self-destruct by mistake during the restart process (#23344)
- Fixed the problem that the checkpoint is left behind due to the abnormal exit of the garbage collection goroutine caused by the etcd restart (#23401)
Enhancement
- Added slow logging performance for query/search when the latency is not less than 5 seconds (#23274)