Unique ID of the Nexfs Server in the Region Cluster

The UUID for the Nexfs server, must be unique to cluster, best to be unique. Nexfs will create a globally unique UUID on initial startup

Nexfs server cluster region (also the services S3 API region)

Must be set to 1 confirm acceptance of Nexustorage T&Cs available at https://www.nexustorage.com/nexustorage-terms-and-conditions

Size of nexfs file dataparts in bytes.

Write buffer size in bytes. The size of incoming write buffers (for receiving data from the kernel)

Enable Write Buffering, group small block writes together to increase performance, a client may receive write ok before data is written to permanent storage.
When enabled, if there is no space available to store written data for an already open file, Nexfs will not return from that write request until space becomes available to secure that data.
Additionally, if nexfs is paused and a write request for an already open file is received, nexfs will not complete that request until nexfs is unpaused. When not enabled, write requests that cannot be written to permanent due to no available space, the request will return instantly, informing the caller that the storage is full and the request was not successful. When nexfs is paused, write requests will return EAGAIN: resource busy, try again

When enabled, the ctime of a file stat result is always set to the current time of the stat operation, NFSv4 clients can rely heavily on ctime changing to manage their internal cache. This setting is recommended for Nfsv4 use cases

Load data chunk into a a lower buffer on read from Tier3+

The maximum length in characters of a file name including its full path that Nexfs can process.

The upper limit will soon be increased to 65536

The maximum number of in memory dataparts that nexfs can have open for each open file handle.

More handles allows more concurrent client requests to be serviced for each open filehandle, and allows more dataparts to be cached in memory. To many parts can lower IO as nexfs needs to scan each cached datapart for a match for every read/wrtie request.

The number of nano seconds to wait between attempts to take a buffer lock.

Having this set to large will reduce performance with nexfs is sleeping, having it to low will increase CPU usage as nexfs attempts to take unavailable buffer locks more often.

Max number of open file handles Nexfs can support (includes all internal file handles)

The number of errors received when writing to the active structure data volume that triggers a failover to the replication volume

If enabled, any data previously cached for a file will be dropped when the file is re-opened.
Enabling this can negatively impact performance

Enable the Nexfs integrated SSL Management web server

Maximum number of concurrent managment webserver connection requests, management webserver must be stopped for liveupdate

The tcp port the managment web server should listen for requests on

Number of seconds after which a idle management api (and webconsole) token should expire

Enable the Nexfs integrated management web server