jingkl

server-instance fouram-cron-1659974400-6 server-configmap server-single-16c64m client-configmap client-search-sift50m-ivf-flat-2048 master-20220805-c5c3392 2.1.1dev3 ``` fouram-cron-1659974400-6-etcd-0 1/1 Running 0 113s 10.104.1.62 4am-node10 fouram-cron-1659974400-6-milvus-standalone-8fc9d59dc-6j8hz 1/1 Running 0 113s 10.104.5.107 4am-node12 fouram-cron-1659974400-6-minio-5d4cfb9b75-59hwg 1/1 Running 0 113s 10.104.1.48 4am-node10...

server-instance fouram-cluster-cron-1661115600-1 server-configmap server-single-32c128m client-configmap client-get-local50m-512 master-20220820-e712b23 2.2.0dev3 ``` fouram-cluster-cron-1661115600-1-etcd-0 1/1 Running 0 2m3s 10.104.1.11 4am-node10 fouram-cluster-cron-1661115600-1-milvus-standalone-64bdc94vw5mx 1/1 Running 0 2m3s 10.104.4.19 4am-node11 fouram-cluster-cron-1661115600-1-minio-6d54578987-5tmxr 1/1 Running 0 2m3s 10.104.4.13 4am-node11...

server-instance fouram-cron-1664208000-7 server-configmap server-cluster-16c64m client-configmap client-search-sift50m-ivf-flat-2048 master-20220926-911ea6c2 2.2.0.dev30 ``` NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES fouram-cron-1664208000-7-etcd-0 1/1 Running 0 5m52s 10.104.1.45 4am-node10 fouram-cron-1664208000-7-etcd-1 1/1 Running...

server-instance fouram-r6z57-1 server-configmap server-single-16c64m client-configmap client-search-sift50m-ivf-flat-2048、 master-20220929-3a770f7d 2.2.0dev32 ``` fouram-r6z57-1-etcd-0 1/1 Running 0 17m 10.104.4.67 4am-node11 fouram-r6z57-1-milvus-standalone-779cb8b9d-mqlf2 1/1 Running 0 17m 10.104.1.18 4am-node10 fouram-r6z57-1-minio-7d6b5696df-52kbx 1/1 Running 0 17m 10.104.4.68 4am-node11...

This hasn't been fixed yet @xige-16

benchmark-backup-ftb4m server-configmap server-cluster-8c64m client-configmap client-random-locust-100m-ddl-r8-w2 client pod：benchmark-backup-ftb4m-4022360165 client log： ``` [2022-04-12 13:00:17,228] [ DEBUG] - 0 users have been stopped, 4 still running (locust.runners:271) [2022-04-12 13:05:17,234] [ ERROR] - grpc...

server-instance benchmark-tag-no-clean-9ndwc-1 server-configmap server-single-32c128m client-configmap client-random-locust-100m-ddl-r8-w2 ``` benchmark-tag-no-clean-9ndwc-1-etcd-0 1/1 Running 0 2d14h 10.97.16.117 qa-node013.zilliz.local benchmark-tag-no-clean-9ndwc-1-milvus-standalone-795f84b4bsx6q9 1/1 Running 0 2d14h 10.97.20.146 qa-node018.zilliz.local benchmark-tag-no-clean-9ndwc-1-minio-f75cd79fd-b72g8 1/1 Running 0 2d14h 10.97.19.164 qa-node016.zilliz.local ``` error:...

server-instance fouram-tag-no-clean-g4m6q-1 server-configmap server-single-32c128m-redur0 client-configmap client-random-locust-100m-ddl-r8-w2-60h 2.1.0-20220819-671d629f pymilvus:2.1.1.dev3 Verified, the problem has not yet appeared, first close issue

> For vector similarity search, I think you can maintain your own repo (w/o being coupled to Serving), right? It's how Google's ScaNN has done it anyway. We would like...

server-configmap server-single-8c32m client-configmap client-random-locust-hnsw-compaction-search-5h image: 2.2.0-20221130-c5f215da pymilvus:2.2.0dev72 This problem no longer arises