vmstorage: high memory used after expanding disk size about victoriametrics

[zekker6]

Hello @tripitakav
This is usually a caused by vmstorage starting background merges. Before the disk expansion vmstorage could postpone merges as there was not enough free disk space to perform a merge. After the disk resize vmstorage detected that there is enough disk space to perform background merge and started merging the data.
You can confirm if that's the case by checking "Active merges" and "Merge" speed panels. If that is the case you will see than number of merges and their speed was lower before the disk resize.

[tripitakav]

@zekker6
Yes, there is indeed a backend merge. Name is indexdb/file.
So is there any way to reduce memory usage？

[zekker6]

@tripitakav Usually, 3-5Mil merge speed should not use that much memory. Could you gather memory profile from the storage nodes as per this instruction and share the profiles here?

[hagen1778]

@tripitakav could you please share screenshots of the Troubleshooting and Interconnection section of the Grafana dashboard?

Btw, I see you have a plenty of restart annotations on the screenshots. Why it is so?

[tripitakav]

@zekker6 @hagen1778
Sorry, I took a leave last week and the old cluster has been deleted by my colleagues, so I cannot see any information. I will temporarily close this issue for now