Updating number of connections to NFSv3 datastore mounted with nConnect feature.
search cancel

Updating number of connections to NFSv3 datastore mounted with nConnect feature.

book

Article ID: 313223

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

This article presents the details about the capability of incrementing/decrementing connections of nConnect feature in ESXi NFS client.

Environment

VMware vSphere 8.02

Resolution

In 8.0u1, a preliminary support for nConnect was published. This feature allows multiple connections to an NFSv3 datastore, it provided an option to increase the number of connections. But in that release there was no way to decrease the total number of connections to an already mounted NFSv3 datastore.

This feature update will allow the decrement of the total number of connections to an already mounted NFSv3 datastore.

For an existing NFSv3 datastore, the number of connections can be increased or decreased at run time using the following command:
esxcli storage nfs param set -v <volume-label> -c <number_of_connections>

This command is a synchronous command i.e., the user CLI is blocked until the operation is complete. The successful completion of this command results in the connections to be set to the desired number and any unused connections will be cleaned up.

This command may fail due to several reasons and appropriate error message will be displayed with the reason for failure. If this command is failed due to any error, the existing number of connections stays the same as the old value. Here are the list of scenarios where this command can fail.

  1. Datastore is in APD state - If the datastore is in APD state, any attempt to increase/decrease the connections will be failed with "No connection" error message.

  2. Parallel updates - If a connection update is in progress, any other parallel update will fail with "Operation now in progress" error message.

  3. Busy Timeout - If the number of connections are getting decreased, the command will busy wait until all the outstanding I/Os on the connections are removed. If the I/Os are not completed within this timeout, the command will fail with "Timeout" error. The default busy wait timeout is 10 seconds, if the decrement connections is failing with Timeout due to busy I/Os, this default timeout can be changed with advanced config command:

esxcfg-advcfg -s <Timeout Value in Seconds> /NFS/ConnectionCleanupTimeout
Powered by Wolken Software