yesyue
yesyue
i hava this issue too , the data increase , it will happen
the attu-client show the error msg follow: show collection failed: load segment failed, OOM if load, maxSegmentSize = 205.4959774017334 MB, memUsage = 121813.59168624878 MB, predictMemUsage = 122019.08766365051 MB, totalMem =...
segment: assignmentExpiration: 2000 compactableProportion: 0.85 diskSegmentMaxSize: 2048 enableLevelZero: true expansionRate: 1.25 maxBinlogFileNumber: 32 maxIdleTime: 600 maxLife: 86400 maxSize: 1024 minSizeFromIdleToSealed: 16 sealProportion: 0.12 smallProportion: 0.5
only one query node mem high, and increasing [querynode (3).log](https://github.com/milvus-io/milvus/files/15206378/querynode.3.log) 
Referring to the Sizing Tools, allocate Data Nodes with 2 cores of 8 GB x 2 pods. However, during actual operation, the Data Nodes was an OOM, and after expansion,...
datanode log: [datanode.log](https://github.com/milvus-io/milvus/files/15145433/datanode.log)
100 Million/day entites write to milvus
[querynode (3).log](https://github.com/milvus-io/milvus/files/15206370/querynode.3.log)