demo
. To add this filesystem to a host, SSH into one of the hosts and run the mount
command as the root
user, as follows:mount
command for a Weka filesystem is:--auth-required
flag to yes
. For more information refer to Mount Authentication section.1.2.3.4
, running the following command as root
on a client will install the agent:curl http://1.2.3.4:14000/dist/v1/install | sh
mount -t wekafs
:/
or /
):mount -t wekafs -o <options> <backend0>[,<backend1>,...,<backendN>]/<fs> <mount-point>
mount -t wekafs -o <options> <backend0>[,<backend1>,...,<backendN>]:/<fs> <mount-point>
options
backend
fs
mount-point
-o
flag to mount.
readcache
writecache
dentry_max_age_positive
dentry_max_age_negative
ro
rw
inode_bits
verbose
quiet
acl
mask
permissions). When ACLs defined but the mount has no ACL, the effective group permissions are granted.)noatime
strictatime
relatime
relatime_threshold
has passed.relatime_threshold
relatime
is on.nosuid
suid
/sgid
bits into effect.nodev
noexec
file_create_mask
file_create_mask
is 770, the file will be created with 770 permissions. umask
is taken into account, followed by the file_create_mask
and then the force_file_mode
.Remount Supported
in the above table can be remounted (using mount -o remount
). When a mount option has been explicitly changed previously, it should be set again in the remount operation to make sure it retains its value. For example, if you mounted with ro
, a remount without it will default to rw
, while if you mounted with rw
, it is not required to be re-specified since this is the default). memory_mb=<memory_mb>
num_cores=<frontend-cores>
<num_cores>
or<core>
can be specified, but not both.net=udp
.core=<core>
net=<netdev>[/<ip>/<bits>[/<gateway>]]
bandwidth_mbps=<bandwidth_mbps>
remove_after_secs=<secs>
traces_capacity_mb=<size-in-mb>
reserve_1g_hugepages
readahead_kb=<readahead>
auth_token_path
~/.weka/auth-token.json
dedicated_mode
full
or none
full
) or not (none
). none can only be set when the NIC driver supports it, as described in DPDK Without Core Dedication section. This option is relevant when using DPDK networking (net=udp
is not set).full
qos_preferred_throughput_mbps
qos_max_throughput_mbps
core
parameters can be used to allocate specific cores to the WekaFS client. E.g., mount -t wekafs -o core=2 -o core=4 -o net=ib0 backend-host-0/my_fs /mnt/weka
mount -t wekafs -o num_cores=1 -o net=ib0 backend-host-0/my_fs /mnt/weka
backend-host-0
and create a Weka container that 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 /mnt/weka
mount -t wekafs -o num_cores=2 backend1,backend2,backend3/my_fs /mnt/weka
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.cd /mnt/weka/
command.umount
command which unmounts the last Weka 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.Remount Supported
in the above table can be remounted (using mount -o remount
). When a mount option is not set in the remount operation, it will retain its current value. To set a mount option back to its default value, use the default
modifier (e.g., memory_mb=default)
.-o net=<netdev>
mount option with the various modifiers as described below.<netdev>
is either the name, MAC address, or PCI address of the physical network device (can be a bond device) to allocate for the client.wekafs
mounts, both clients and backends should use the same type of networking technology (either IB or Ethernet).net=<netdev>/[ip]/[bits]/[gateway]
.ip, bits, gateway
are optional. In case they are not provided, the Weka system tries to deduce them when in AWS or IB environments, or allocate them from the default data network otherwise. If both approaches fail, the mount command will fail.-o net
notation shown in the examples above can be used to pass the names of specific NICs to the WekaFS host driver.-o mgmt_ip=<ip>+<ip2>
command-line option.ha
is used here, which stands for using the device on all processes.-o num_cores
), it is possible to control what processes use what NICs. This can be accomplished through the use of special command line modifiers called slots. In WekaFS, slot is synonymous with a process number. Typically, the first WekaFS Frontend process will occupy slot 1, then the second - slot 2 and so on.s1
, s2
, s2+1
, s1-2
, slots1+3
, slot1
, slots1-4
, where -
specifies a range of devices, while +
specifies a list. For example, s1-4
implies slots 1, 2, 3 and 4, while s1+4
specifies slots 1 and 4 only.mlnx0
is bound to the second Frontend process whilemlnx1
to the first one for improved performance.mlnx0
, mlnx1
) are allocated. By explicitly specifying s2+1
, s1-2
modifiers for network devices, both devices will be used by both Frontend processes. Notation s2+1
stands for the first and second processes, while s1-2
stands for the range of 1 to 2, and are effectively the same.net=udp
in the mount command to set the UDP networking mode, for example:systemd
(e.g.: RHEL/CentOS 7.2 and up, Ubuntu 16.04 and up, Amazon Linux 2 LTS)./etc/fstab
file to include the filesystem mount entry:wekafs
systemd
to wait for the weka-agent
service to come up, and set the filesystem as a network filesystem, e.g.:x-systemd.requires=weka-agent.service,x-systemd.mount-timeout=infinity,_netdev
wekafs
supported mount optionsystemd
unit to be created and marked correctly.umount
), as the systemd
needs to mark the filesystem as a network filesystem (occurs as part of the reboot
). Trying to reboot a host when there is a mounted WekaFS filesystem when setting its fstab
configuration might yield a failure to unmount the filesystem and leave the system hanged.autofs
command.autofs
on the host:autofs
configuration files for Weka filesystems:autofs
service:autofs
service automatically starts after restarting the server, run the following command: systemctl is-enabled autofs.
If the output is enabled
the service is configured to start automatically.autofs
service can be verified with chkconfig
command. If the output is on
for the current runlevel (can be checked with runlevel
command), autofs
will be enabled upon reboot.cd /mnt/weka/<fs-name>
command.