elstic
elstic
Continuous search in the growing segment phase, with some search errors. client pod: new-stable-master-1705600800-2994728836 client error log: ``` [2024-01-18 18:35:31,116 - INFO - fouram]: (stats.py:820) [2024-01-18 18:35:47,596 - ERROR -...
> do we have any coredump file for this run? @elstic No. It's not on by default. Do you need coredump?
@congqixia It may be an occasional problem, it didn't show up in yesterday's nighlty
The issue has come up again. case: test_concurrent_locust_diskann_dml_dql_filter_standalone server: ``` fouram-disk-sta52400-6-77-9926-etcd-0 1/1 Running 0 11m 10.104.23.98 4am-node27 fouram-disk-sta52400-6-77-9926-milvus-standalone-87598bd947x9zr 1/1 Running 2 (108s ago) 11m 10.104.33.145 4am-node36 fouram-disk-sta52400-6-77-9926-minio-5d9d7f6448-9zggt 1/1 Running 0...
#### Some flushes fail during concurrency testing case: test_concurrent_locust_diskann_compaction_cluster image: 2.3-20240115-f2a0c3f0-amd64 test steps: ``` 1. create a collection or use an existing collection 2. build an DiskANN index on the...
#### When load, search, query, and upsert concurrently, milvus reboots and search/query reports an error. image : master-20240118-ddccccbc-amd64 argo task : new-stable-master-1705600800 , id: 7 client pod: new-stable-master-1705600800-480296231 (qa namespace,...
> Can this issue be reproduced? @jiaoew1991 Yes, it must be present; verified again, using the image : master-20230614-35cb0b5b
No more oom, but now concurrently querying the return vector still gives an error. keep an eye on this issue: https://github.com/milvus-io/milvus/issues/25996
>  the total data size to load already reach the memory limit of query node, so the collection can't be loaded and there are no available shard to provide...
If no vector is returned and 100m of data is inserted and tested concurrently, querynode's memory usage is 33G*2; Returning vector and float scalar, inserting 100m data and testing concurrently,...