NFS advanced configuration option MaxQueueDepth does not work as intended
Article ID: 318508
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
The maximum queue depth specified in MaxQueueDepth advanced configuration option is not reflected in NFS datastores
The maximum queue depth specified in MaxQueueDepth advanced configuration option is not reflected in NFS datastores
Environment
VMware vSphere ESXi 7.0.1
VMware vSphere ESXi 7.0.2
VMware vSphere ESXi 7.0.2
Cause
From ESXi version 7.0U1, configurations are stored in config store. While mounting the NFS datastore the global maxQDepth value is not taken into consideration, instead it is set to the default value from config store.
Resolution
Fixed in vSphere 7.0U3 and later versions
Workaround:
The maximum queue depth needs to be set on individual NFS datastores on all hosts. The following commands can be used to set and get the maximum queue depth value on a single NFS datastore.
esxcli storage nfs param set -q <value> -v <nfs_volume_label>
esxcli storage nfs param get -v <nfs_volume_label>
Workaround:
The maximum queue depth needs to be set on individual NFS datastores on all hosts. The following commands can be used to set and get the maximum queue depth value on a single NFS datastore.
esxcli storage nfs param set -q <value> -v <nfs_volume_label>
esxcli storage nfs param get -v <nfs_volume_label>
Feedback
Yes
No
Powered by
