Additional mount options using the stateless clients feature

Content Software for File CLI Reference

Part Number
Option Value Description Default Remount Supported
Number Amount of memory to be used by the client (for huge pages). 1400 MiB Yes
Number The number of frontend cores to allocate for the client. Either <num_cores> or <core> can be specified, but not both. If none are specified, the client will be configured with 1 core. If 0 is specified then you must use net=udp. 1 No
Number Specify explicit cores to be used by the Content Software for File FS client. Multiple cores can be specified. Core 0 is not allowed.   No
String For more info refer to Advanced network configuration using mount options section.   No
Number Maximum network bandwidth in Mb/s, which limits the traffic that the container can send. Auto-select Yes
Number The number of seconds without connectivity after which the client will be removed from the cluster. Minimum value: 60 seconds. 86,400 seconds (24 hours) Yes
Number Traces capacity limit in MB. Minimum value: 512 MB.   No
None Controls the page allocation algorithm if to reserve only 2MB huge pages or also 1GB ones. Yes Yes
Number in KB Controls the readahead per mount (higher readahead better for sequential reads of large files). 32768 Yes
String Path to the mount authentication token (per mount).
dedicated_mode full or none Determine whether DPKD networking dedicates a core (full) or not (none). none can only be set when the NIC driver supports it. See DPDK Without Code Dedication section.This option is relevant when using DPDK networking (net=udp is not set). full  
qos_preferred_throughput_mbps Number Preferred requests rate for QoS in megabytes per second. No limit. The cluster admin can set this default. See mount option defaults. Yes
qos_max_throughput_mbps Number Maximum requests rate for QoS in megabytes per second. This option allows bursting above the specified limit but aims to keep this limit on average. No limit. The cluster admin can set this default. See mount option defaults. Yes
qos_max_ops Number Maximum number of IO operations a client can perform per second. Set a limit to a client or clients to prevent starvation from the rest of the clients. No limit. Do not set this option for mounting from a backend. Yes
connect_timeout_secs Number The timeout in seconds for establishing a connection to a single host.
 10 Yes
response_timeout_secs Number The timeout in seconds for waiting for the response from a single host. 60 Yes
join_timeout_secs Number The timeout, in seconds, for the client container to join the Content Software for File cluster. 360 Yes
Note: These parameters, if not stated otherwise, are only effective on the first mount command for each client.
Note: By default, the command selects the optimal core allocation for Content Software for File. If necessary, multiple core parameters can be used to allocate specific cores to the WekaFS client. For example,
mount -t wekafs -o core=2 -o core=4 -o net=ib0 backend-host-0/my_fs /mnt/weka

On-Premise Installations

mount -t wekafs -o num_cores=1 -o net=ib0 backend-host-0/my_fs /mnt/weka

Running this command on a host installed with the Content Software for File agent will download the appropriate version from the host backend-host-0 and create a container which allocates a single core and a named network interface ib0. Then it will join the cluster that backend-host-0 is part of and mount the filesystem my_fs on /mnt/weka.

mount -t wekafs -o num_cores=0 -o net=udp backend-host-0/my_fs

Running this command will use UDP mode (usually selected when the use of DPDK is not available).

For stateless clients, the first mount command installs the weka client software and joins the cluster). Any subsequent mount command, can either use the same syntax or just the traditional/per-mount parameters as defined in Mounting Filesystems since it is not necessary to join a cluster.

It is now possible to access Content Software for File filesystems via the mount-point, by the cd /mnt/weka/ command.

After the execution of anumount command, which unmounts the last Content Software for File filesystem, the client is disconnected from the cluster and will be uninstalled by the agent. Consequently, executing a new mount command requires the specification of the cluster, cores, and networking parameters again.

Note: Memory allocation for a client is predefined. Contact your Hitachi representative when it is necessary to change the amount of memory allocated to a client.