Repository navigation
Running Milvus 2.6.x on an Ubuntu 24.04 base image (from 22.04): any functional or performance concerns? #55438
Replies: 3 comments
|
Thanks for the detailed write-up — the packaging steps you described match the current tree. On the images: the official 2.6.x / The I would not treat running the official 22.04-built 2.6.x binaries on a self-built Ubuntu 24.04 runtime image as a supported configuration. For production, the safer option is to keep using the official 22.04 runtime image and only change the Milvus version. A 24.04 repack is at your own risk until upstream ships and tests one. I have not found a dedicated tracking issue for an official Ubuntu 24.04 runtime image; whether one is planned for 2.6.x or 3.x is better left for maintainers to confirm. I also do not have a definitive official list of functional or performance regressions from 2.6.22 to 2.6.26. The dependency changes you already noted (librdkafka 1.9.1 → 2.6.1, and OpenBLAS now statically linked via Conan) are worth putting on the test plan — especially message-queue paths and BLAS-heavy search — alongside the userland change (glibc 2.35 → 2.39, libstdc++, libgomp, libaio). |
|
@xiaofan-luan @liliu-z Could a maintainer confirm two points when you have a moment?
Thanks. |
|
On the libaio and userland questions (Q1 and Q3): The symlink is fine on x86_64. The I also ran the v2.6.26 binaries on Ubuntu 24.04 with only that symlink added (standalone, embedded etcd, local storage). Milvus started, built and loaded a DISKANN index, and searches returned the right ids. What the base image actually changes: going by |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Background
We run Milvus 2.6.22 in cluster mode on Kubernetes. Our image is repackaged: we copy
/milvus(bin, lib, configs) from the officialmilvusdb/milvusimage onto our own Ubuntu base image, following the upstreambuild/docker/milvus/ubuntu22.04/Dockerfile.We plan to upgrade to 2.6.26 and, in the same change, move the runtime base image from Ubuntu 22.04 to Ubuntu 24.04. The Kubernetes node OS and kernel stay the same; only the container base image changes.
We want to confirm that this move does not affect Milvus functionality or performance in general. We use features such as mmap and tiered storage eviction, but the question is about the runtime as a whole rather than one feature.
What we checked
masterare all built onubuntu:jammy-20240530.masterhas abuild/docker/builder/cpu/ubuntu24.04builder image, but there is nobuild/docker/milvus/ubuntu24.04runtime Dockerfile./milvusfrommilvusdb/milvus:v2.6.26ontoubuntu:noblewith the same apt packages as the upstream Dockerfile (curl libaio-dev libgomp1 libopenblas-dev):error while loading shared libraries: libaio.so.1: cannot open shared object file. On 24.04 the library is shipped aslibaio.so.1t64(64-bit time_t transition) and there is nolibaio.so.1.ln -s libaio.so.1t64 /usr/lib/x86_64-linux-gnu/libaio.so.1,lddreports no missing libraries and the process starts.openssl fipsinstallwith/milvus/lib/ossl-modules/fips.sopasses.Questions
libaio.so.1symlink an acceptable workaround, or is there a known problem with the t64 variant of libaio?dynamic_arch).Any guidance or experience from others running Milvus on Ubuntu 24.04 would be appreciated.
All reactions