[Bug]: [configuration] cannot change the localStorage path if milvus is deployed by helm about milvus HOT 8 OPEN

/assign @LoveEachDay
please help to take a look

/unassign

from milvus.

@LoveEachDay Hello! Could you help to look?

from milvus.

we should fix that on next version of helm chart.

@zwd1208 and should ensure there is no more hard coded configs

from milvus.

@tianshihan818
The root cause of the issue is the use of the emptyDir volume type here, which uses the kubelet working directory as storage. For chunk cache, we recommend using local NVMe disks to achieve better performance. Therefore, the usual approach we suggest is: 1) Schedule the querynode to a worker node with local NVMe disks. 2) Modify the working directory of kubelet in the worker node with local NVMe disks to point to the NVMe disk's directory.

from milvus.

@tianshihan818 The root cause of the issue is the use of the emptyDir volume type here, which uses the kubelet working directory as storage. For chunk cache, we recommend using local NVMe disks to achieve better performance. Therefore, the usual approach we suggest is: 1) Schedule the querynode to a worker node with local NVMe disks. 2) Modify the working directory of kubelet in the worker node with local NVMe disks to point to the NVMe disk's directory.

why can not user specify the disk they want to use?
The problem is helm chard hard coded /var/lib

from milvus.

@xiaofan-luan ok, we will support all storage path related configuration in the next version of helm chart and operator.

from milvus.

We'll add a extra hostPath volume type which allow user to specify extra disk path to store disk index data and chunk cache, other than default /var/lib/kubelet.

from milvus.

Thanks all! This will be much helpful!

from milvus.