Open wangting0128 opened 2 weeks ago
We previously used mmap to load raw data when the index did not already contain it. Now, this process is controlled by the queryNode.mmap.scalarField configuration. By default, queryNode.mmap.scalarField is set to false, so raw data will be loaded into memory instead, which typically consumes around 30GB.
Please set queryNode.mmap.scalarField to true and retest it.
Please set queryNode.mmap.scalarField to true and retest it.
argo task:fouramf-mnc77 test case name:test_inverted_locust_varchar_dml_dql_cluster image:2.4-20240902-90147b13-amd64
server:
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
fouramf-mnc77-73-4449-etcd-0 1/1 Running 0 4h16m 10.104.32.122 4am-node39 <none> <none>
fouramf-mnc77-73-4449-etcd-1 1/1 Running 0 4h16m 10.104.17.115 4am-node23 <none> <none>
fouramf-mnc77-73-4449-etcd-2 1/1 Running 0 4h16m 10.104.18.19 4am-node25 <none> <none>
fouramf-mnc77-73-4449-milvus-datanode-55cd88cc6c-n6fbm 1/1 Running 2 (4h11m ago) 4h16m 10.104.23.248 4am-node27 <none> <none>
fouramf-mnc77-73-4449-milvus-indexnode-7c99465cfc-wjgmw 1/1 Running 1 (4h15m ago) 4h16m 10.104.20.231 4am-node22 <none> <none>
fouramf-mnc77-73-4449-milvus-mixcoord-7956f866bb-rbs6q 1/1 Running 2 (4h11m ago) 4h16m 10.104.20.230 4am-node22 <none> <none>
fouramf-mnc77-73-4449-milvus-proxy-7f858656b6-glnkd 1/1 Running 2 (4h11m ago) 4h16m 10.104.20.229 4am-node22 <none> <none>
fouramf-mnc77-73-4449-milvus-querynode-5b469746c5-hx96q 1/1 Running 1 (4h15m ago) 4h16m 10.104.21.65 4am-node24 <none> <none>
fouramf-mnc77-73-4449-minio-0 1/1 Running 0 4h16m 10.104.32.121 4am-node39 <none> <none>
fouramf-mnc77-73-4449-minio-1 1/1 Running 0 4h16m 10.104.17.114 4am-node23 <none> <none>
fouramf-mnc77-73-4449-minio-2 1/1 Running 0 4h16m 10.104.18.17 4am-node25 <none> <none>
fouramf-mnc77-73-4449-minio-3 1/1 Running 0 4h16m 10.104.33.15 4am-node36 <none> <none>
fouramf-mnc77-73-4449-pulsar-bookie-0 1/1 Running 0 4h16m 10.104.32.123 4am-node39 <none> <none>
fouramf-mnc77-73-4449-pulsar-bookie-1 1/1 Running 0 4h16m 10.104.33.13 4am-node36 <none> <none>
fouramf-mnc77-73-4449-pulsar-bookie-2 1/1 Running 0 4h16m 10.104.17.119 4am-node23 <none> <none>
fouramf-mnc77-73-4449-pulsar-bookie-init-2m4qx 0/1 Completed 0 4h16m 10.104.14.155 4am-node18 <none> <none>
fouramf-mnc77-73-4449-pulsar-broker-0 1/1 Running 0 4h16m 10.104.14.156 4am-node18 <none> <none>
fouramf-mnc77-73-4449-pulsar-proxy-0 1/1 Running 0 4h16m 10.104.17.110 4am-node23 <none> <none>
fouramf-mnc77-73-4449-pulsar-pulsar-init-7k5fh 0/1 Completed 0 4h16m 10.104.32.116 4am-node39 <none> <none>
fouramf-mnc77-73-4449-pulsar-recovery-0 1/1 Running 0 4h16m 10.104.6.70 4am-node13 <none> <none>
fouramf-mnc77-73-4449-pulsar-zookeeper-0 1/1 Running 0 4h16m 10.104.17.116 4am-node23 <none> <none>
fouramf-mnc77-73-4449-pulsar-zookeeper-1 1/1 Running 0 4h15m 10.104.33.17 4am-node36 <none> <none>
fouramf-mnc77-73-4449-pulsar-zookeeper-2 1/1 Running 0 4h14m 10.104.30.7 4am-node38 <none> <none>
After setting the configuration, verification is passed
Please help confirm whether the behavior of the newly added default configuration causing increased memory usage is by design, thanks @yanliang567 @xiaofan-luan @SimFG
do we enable the old configs? maybe the old config is invalid due to the config change. we should fix that if this is a config issue
do we enable the old configs? maybe the old config is invalid due to the config change. we should fix that if this is a config issue
@SimFG Please help look at this issue,thanks
This is a bug that existed before. Regardless of whether mmap is enabled or not, for an index without raw data, additional raw data is loaded using mmap. This PR has corrected this behavior. https://github.com/milvus-io/milvus/pull/35359/files#diff-ab3e84c35be9928ca123b7d966c7d346525ab2b4080dac5006fd28a853a4b6c9
This is a bug that existed before. Regardless of whether mmap is enabled or not, for an index without raw data, additional raw data is loaded using mmap. This PR has corrected this behavior. https://github.com/milvus-io/milvus/pull/35359/files#diff-ab3e84c35be9928ca123b7d966c7d346525ab2b4080dac5006fd28a853a4b6c9
Actually it's not a bug, we intend to mmap load raw data to save some memory if an index does not contain it.
This is a bug that existed before. Regardless of whether mmap is enabled or not, for an index without raw data, additional raw data is loaded using mmap. This PR has corrected this behavior. https://github.com/milvus-io/milvus/pull/35359/files#diff-ab3e84c35be9928ca123b7d966c7d346525ab2b4080dac5006fd28a853a4b6c9
Now that this error has been corrected, the previous scenario fails to run :<
Is there an existing issue for this?
Environment
Current Behavior
same case, different image
test case name: test_inverted_locust_varchar_dml_dql_cluster
Problem image:2.4-20240831-8b706122-amd64 server:
queryNode memory usage ~ 30G
Normal image:2.4-20240807-b22f3a62-amd64 server:
Expected Behavior
No response
Steps To Reproduce
Milvus Log
No response
Anything else?
normal test result: