milvus: [Bug]: [benchmark] milvus insert data datanode memory rise
Is there an existing issue for this?
- I have searched the existing issues
Environment
- Milvus version:2.2.0-20230410-d845175f
- Deployment mode(standalone or cluster):cluster
- MQ type(rocksmq, pulsar or kafka):
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
Current Behavior
1b data continuous search test scenario, before inserting 1b data datanode memory use no more than 1.4G, but now the same insert frequency, datanode memory use more than 3G, and is still growing.
image: 2.1.0-20220726-1b33c731
datanode memory usage (709m + 733m combined does not exceed 1.4G) :
image: 2.2.0-20230410-d845175f
qtp-1b-test-lbcyr-etcd-0 1/1 Running 0 6m23s 10.104.5.110 4am-node12 <none> <none>
qtp-1b-test-lbcyr-etcd-1 1/1 Running 0 6m22s 10.104.6.235 4am-node13 <none> <none>
qtp-1b-test-lbcyr-etcd-2 1/1 Running 0 6m22s 10.104.4.48 4am-node11 <none> <none>
qtp-1b-test-lbcyr-milvus-datacoord-5b489d5f57-dnvw7 1/1 Running 0 6m23s 10.104.4.31 4am-node11 <none> <none>
qtp-1b-test-lbcyr-milvus-datanode-5888986546-9kkjt 1/1 Running 1 (2m22s ago) 6m23s 10.104.6.228 4am-node13 <none> <none>
qtp-1b-test-lbcyr-milvus-indexcoord-6bd8dd4d7-jrjj2 1/1 Running 1 (2m22s ago) 6m23s 10.104.4.33 4am-node11 <none> <none>
qtp-1b-test-lbcyr-milvus-indexnode-58b84db4c8-ctldx 1/1 Running 0 6m23s 10.104.9.122 4am-node14 <none> <none>
qtp-1b-test-lbcyr-milvus-proxy-7b9c67b545-st8ch 1/1 Running 1 (2m22s ago) 6m23s 10.104.5.101 4am-node12 <none> <none>
qtp-1b-test-lbcyr-milvus-querycoord-695fb8f5b-nfmws 1/1 Running 1 (2m22s ago) 6m23s 10.104.4.35 4am-node11 <none> <none>
qtp-1b-test-lbcyr-milvus-querynode-8574948fc4-kn8jz 1/1 Running 0 6m23s 10.104.6.227 4am-node13 <none> <none>
qtp-1b-test-lbcyr-milvus-querynode-8574948fc4-l24r2 1/1 Running 0 6m23s 10.104.9.119 4am-node14 <none> <none>
qtp-1b-test-lbcyr-milvus-querynode-8574948fc4-p5cbs 1/1 Running 0 6m23s 10.104.4.37 4am-node11 <none> <none>
qtp-1b-test-lbcyr-milvus-querynode-8574948fc4-p5rjt 1/1 Running 0 6m23s 10.104.5.100 4am-node12 <none> <none>
qtp-1b-test-lbcyr-milvus-querynode-8574948fc4-vr7vc 1/1 Running 0 6m23s 10.104.4.40 4am-node11 <none> <none>
qtp-1b-test-lbcyr-milvus-querynode-8574948fc4-xf8cn 1/1 Running 0 6m23s 10.104.1.120 4am-node10 <none> <none>
qtp-1b-test-lbcyr-milvus-rootcoord-5fb7645c68-mnpcb 1/1 Running 1 (2m22s ago) 6m23s 10.104.4.34 4am-node11 <none> <none>
qtp-1b-test-lbcyr-minio-0 1/1 Running 0 6m23s 10.104.5.109 4am-node12 <none> <none>
qtp-1b-test-lbcyr-minio-1 1/1 Running 0 6m23s 10.104.6.234 4am-node13 <none> <none>
qtp-1b-test-lbcyr-minio-2 1/1 Running 0 6m22s 10.104.4.46 4am-node11 <none> <none>
qtp-1b-test-lbcyr-minio-3 1/1 Running 0 6m22s 10.104.9.124 4am-node14 <none> <none>
qtp-1b-test-lbcyr-pulsar-bookie-0 1/1 Running 0 6m23s 10.104.5.107 4am-node12 <none> <none>
qtp-1b-test-lbcyr-pulsar-bookie-1 1/1 Running 0 6m23s 10.104.6.233 4am-node13 <none> <none>
qtp-1b-test-lbcyr-pulsar-bookie-2 1/1 Running 0 6m22s 10.104.4.45 4am-node11 <none> <none>
qtp-1b-test-lbcyr-pulsar-bookie-init-qk8wj 0/1 Completed 0 6m23s 10.104.4.38 4am-node11 <none> <none>
qtp-1b-test-lbcyr-pulsar-broker-0 1/1 Running 0 6m23s 10.104.4.36 4am-node11 <none> <none>
qtp-1b-test-lbcyr-pulsar-proxy-0 1/1 Running 0 6m23s 10.104.5.99 4am-node12 <none> <none>
qtp-1b-test-lbcyr-pulsar-pulsar-init-q6n6t 0/1 Completed 0 6m23s 10.104.4.32 4am-node11 <none> <none>
qtp-1b-test-lbcyr-pulsar-recovery-0 1/1 Running 0 6m23s 10.104.4.39 4am-node11 <none> <none>
qtp-1b-test-lbcyr-pulsar-zookeeper-0 1/1 Running 0 6m23s 10.104.5.106 4am-node12 <none> <none>
qtp-1b-test-lbcyr-pulsar-zookeeper-1 1/1 Running 0 5m44s 10.104.6.237 4am-node13 <none> <none>
qtp-1b-test-lbcyr-pulsar-zookeeper-2 1/1 Running 0 5m2s 10.104.4.54 4am-node11 <none> <none>
datanode memory usage:
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 48 (48 by maintainers)
May be fixed by this pr: https://github.com/milvus-io/milvus/pull/29268 No datanode memory hikes.
Verify case : test_concurrent_locust_100m_hnsw_ddl_dql_filter_kafka_cluster