[Bug]: milvus-querynode memory leak

[FmKnight]

[Bug]: milvus-querynode memory leak

[czs007]

@FmKnight it seems that the milvus version is 2.3.4 instead of 2.4.4 ?

commit 7a192da
Author: congqixia [email protected]
Date: Fri Dec 29 18:32:45 2023 +0800

enhance: Bump version 2.3.4 & milvus-proto (#29598)

[tedxu]

The uploaded log may not be specific to the client's case. The log itself looks good.

Additionally, I've observed that the loading segments are relatively small. It would be beneficial if you could examine the datanode logs to verify the effectiveness of the compaction process.

[FmKnight]

@FmKnight it seems that the milvus version is 2.3.4 instead of 2.4.4 ?

commit 7a192da Author: congqixia [email protected] Date: Fri Dec 29 18:32:45 2023 +0800

enhance: Bump version 2.3.4 & milvus-proto (#29598)

@czs007
yes, the log is milvus 2.3.4， we upgrade the version to 2.4.4 on end of June. Is there a memory leak? The milvus-quernode service crashes after a period of use. can we adjust parameters to avoid this or any other solution to avoid this.

[FmKnight]

The uploaded log may not be specific to the client's case. The log itself looks good.

Additionally, I've observed that the loading segments are relatively small. It would be beneficial if you could examine the datanode logs to verify the effectiveness of the compaction process.

@tedxu
i paste our current milvus2.4.4 datanode log below, please see whether this can help find out the problem and solve.
thanks
milvus24-datanode-68977b5876-6hk2r.log

[yanliang567]

/assign @tedxu @czs007
/unassign

[tedxu]

@FmKnight upon reviewing the datanode log, I haven't identified any issues.

It would be helpful if you could upload the complete log file. You can utilize the script found at deployments/export-log/export-milvus-log.sh to extract the most recent logs. Furthermore, please make sure to collect these logs from the right cluster.