Managing clients
How to manage clients using the CLI.
Joining the cluster using the CLI
Commandweka cluster host add
Once the client host is in the stem mode (this is the mode defined immediately after running the install.sh command), use the following command line on the client host to add it to the cluster:
weka -H <backend-hostname> cluster host add <client-hostname>
Parameters
| Name | Type | Value | Limitations | Mandatory | Default |
| backend-hostname | String | IP/hostname of one of the existing backend instances in the cluster | Valid hostname (FQDN or IP) | Yes | |
| client-hostname | String | IP/hostname of the client currently being added | Valid hostname (FQDN or IP) | Yes |
NoteOn completion of this stage, the host-ID of the newly added host will be received. Make a note of it for the next steps.
Configuring the host as client using the CLI
Commandweka cluster host cores
To configure the new host as a client, run the following command:
weka cluster host cores <host-id> <cores> --frontend-dedicated-cores=<fe_cores>
Parameters
| Name | Type | Value | Limitations | Mandatory | Default |
| host-id | String | Identifier of the host to be added to the cluster | Must be a valid host identifier | Yes | |
| cores | Number | Number of physical cores to be allocated to the Content Software for File client | Maximum 19 cores | Yes | |
| frontend-dedicated-cores | Number | Number of physical cores to be dedicated to FrontEnd processes | For clients, the number of total cores and frontenddedicated-cores must be equal | Yes, in order to configure a host as a client |
Configuring client networking using the CLI
Command
weka cluster host net add
NoteIf the new client is to communicate with the Content Software for File system cluster over the kernel UDP stack, it is not necessary to run this command. If a high-performance client is required and the appropriate network NIC is available, use the following command to configure the networking interface used by the client to communicate with the Content Software for File system cluster hosts:
weka cluster host net add <host-id> <device> --ips=<ip-address> --netmask=<netmask> --gateway=<gateway>
Parameters
| Name | Type | Value | Limitations | Mandatory | Default |
| host-id | String | Identifier of the host to be added to the cluster | Must be a valid host identifier | Yes | |
| device | String | Network interface device name for example, eth1 | Must be a valid network device name | Yes | |
| ips | IP address | The IP address of the new interface | Must be a valid IP address | Yes | |
| gateway | IP address | The IP address of the default routing gateway | The gateway must reside within the same IP network of ip-address (as described by netmask). Not relevant for IB / L2 non-routable networks | No | |
| netmask | Number | Number of bits in the net mask, for example, the net mask of 255.255.0.0 has 16 netmask bits | Describes the number of bits that identify a network ID (also known as CIDR) | No |
NoteWhen configuring an InfiniBand client, do not pass the --ips, --netmask, and --gateway parameters.
NoteInfiniBand clients can only join a cluster with InfiniBand backends. It is not possible to mix InfiniBand and Ethernet clients/backends.
Applying the host configuration using the CLI
Command
weka cluster host apply
After successfully configuring the host and its network device, run the following command to finalize the configuration by activating the host:
weka cluster host apply <host-id> [--force]
Parameter
| Name | Type | Value | Limitation | Mandatory | Default |
| hostid | Comma-separated string | Identifier of host to be added to the cluster | Must be a valid host identifier | Yes | |
| force | Boolean | Do not prompt for confirmation | No | Off |