elstic

/unassign @bigsheeper

This issue still exists. image: 2.2.0-20230608-a03ebcff 

> this is as expected? unless datanode reaches certain threshold ton do auto flush? This is not expected, before we 20 concurrently inserted data, daatanode memory does not rise

This issue still exists. Reboot after datanode memory reaches limit . case: test_concurrent_locust_100m_hnsw_ddl_dql_filter_output_kafka_cluster argo task : fouramf-t24hx during time : 192h memory usage ：  datanode memory usage:  ####...

> > > didn't really understand. Datanode memory is only a few giga bytes. It rise becasue datanode accumulate data in memory and decrease when flush happened > > >...

This issue did not reappear. image: 2.2.0-20230604-29579aae

The issue no longer exists and I will close it. Verify version: 2.2.0-20230801-53a23fc8

> @elstic @jiaoew1991 is it a dup of #23331? > They have similarities and report similar errors. But there are also differences, #23331 is cluster and FLAT, this issue is...

> @elstic could you help check whether the problem still exists, as #23331 has fixed? This issue still exists. I briefly describe my behavior: 1. initialize milvus instance with milvus...

### [cluster] load memory usage more #### Current Behavior Adjusting memory usage before load：4.3G (querynode)  Adjusting memory usage after load： 5.5G (querynode)