W E K A
3.14
3.14
  • WEKA v3.14 Documentation
  • Weka System Overview
    • About the WEKA System
    • SSD Capacity Management
    • Filesystems, Object Stores & Filesystem Groups
    • Weka Networking
    • Data Lifecycle Management
    • Weka Client & Mount Modes
    • Glossary
  • Getting Started with Weka
    • Quick Install Guide
    • Managing the Weka System
    • CLI Overview
    • GUI Overview
    • Serving IOs with WekaFS
  • Planning & Installation
    • Prerequisites for Installation
    • Bare Metal Installation
      • Planning a Weka System Installation
      • Setting Up the Hosts
        • SR-IOV Enablement
      • Obtaining the Weka Install File
      • Weka System Installation Process Using the CLI
      • Adding Clients
    • AWS Installation
      • Self-Service Portal
      • CloudFormation Template Generator
      • Deployment Types
      • AWS Outposts Deployment
      • Supported EC2 Instance Types
      • Adding Clients
      • Auto Scaling Group
      • Troubleshooting
  • Performance
    • Testing Weka Performance
      • Test Environment Details
  • WekaFS Filesystems
    • Managing Filesystems, Object Stores & Filesystem Groups
      • Managing Object Stores
      • Managing Filesystem Groups
      • Managing Filesystems
      • Attaching/Detaching Object Stores to/from Filesystems
      • KMS Management
    • Advanced Data Lifecycle Management
      • Advanced Time-based Policies for Data Storage Location
      • Data Management in Tiered Filesystems
      • Transition Between Tiered and SSD-Only Filesystems
      • Manual fetch and release of data
    • Mounting Filesystems
    • Snapshots
    • Snap-To-Object
    • Quota Management
  • Additional Protocols
    • NFS
    • SMB
      • SMB Management Using CLIs
      • SMB Management Using the GUI
    • S3
      • S3 Cluster Management
      • S3 Buckets Management
      • S3 Users and Authentication
      • S3 Information Lifecycle Management
      • Audit S3 APIs
      • S3 Limitations
      • S3 Examples using boto3
  • Operation Guide
    • Alerts
      • List of Alerts
    • Events
      • List of Events
    • Statistics
      • List of Statistics
    • System Congestion
    • Security
      • User Management
      • Organizations
    • Expanding & Shrinking Cluster Resources
      • Expand & Shrink Overview
      • Stages in Adding a Backend Host
      • Expansion of Specific Resources
      • Shrinking a Cluster
    • Background Tasks
    • Upgrading Weka Versions
  • Billing & Licensing
    • License Overview
    • Classic License
    • Pay-As-You-Go License
  • Support
    • Prerequisites and Compatibility
    • Getting Support for Your Weka System
    • The Weka Support Cloud
    • Diagnostics CLI Command
  • Appendix
    • Weka CSI Plugin
    • External Monitoring
    • Snapshot Management
  • REST API
Powered by GitBook
On this page
  • About Client Hosts
  • Adding (Stateless) Clients
  • Adding (Stateful) Clients Which Are Always Part of the Cluster
  • Stage 1: Install the Software
  • Stage 2: Joining the Cluster
  • Stage 3: Configuring the Host as Client
  • Stage 4: Configuring Client Networking
  • Stage 5: Applying the Host Configuration
  1. Planning & Installation
  2. Bare Metal Installation

Adding Clients

This page describes how to add clients to a bare-metal cluster.

PreviousWeka System Installation Process Using the CLINextAWS Installation

Last updated 2 years ago

About Client Hosts

Client hosts are used to running applications that need to access the Weka filesystems. They do not contribute CPUs or drives to the cluster and only connect to the cluster to use its filesystems.

Adding (Stateless) Clients

To use the Weka filesystems from a client host, all that is needed is to call the mount command. The mount command automatically installs the software version, and there is no need to join the client to the cluster.

To mount a filesystem in this manner, first, install the Weka agent from one of the backend instances and then mount the filesystem. For example:

# Agent Installation (one time)
curl http://Backend-1:14000/dist/v1/install | sh

# Creating a mount point (one time)
mkdir -p /mnt/weka

# Mounting a filesystem
mount -t wekafs Backend-1/my_fs /mnt/weka

For the first mount, this will install the Weka software and automatically configure the client. For more information on mount and configuration options, refer to .

It is possible to configure the client OS to automatically mount the filesystem at boot time. For more information refer to or .

Note: Clients can be deployed on . They can use RAM for Weka client software and NFS mount for the traces. For more information, contact the Weka Support Team.

Note: The different clients must have a unique IP and FQDN.

Adding (Stateful) Clients Which Are Always Part of the Cluster

Note: It is possible to add instances that do not contribute resources to the cluster but are used for mounting filesystems. It is recommended to use the previously described method for adding client instances for mounting purposes. However, in some cases it could be useful to permanently add them to the cluster, e.g., to use these instances as NFS/SMB servers which are always expected to be up.

Stage 1: Install the Software

Note: All hosts (clients and backends) in a Weka system cluster must use the same software version. If attempts are made to mix multiple versions, the new hosts will fail to join the cluster.

Stage 2: Joining the Cluster

Command: weka cluster host add

Once the client host is in the stem mode (this is the mode defined immediately after running the install.shcommand), 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 in Command Line

Name

Type

Value

Limitations

Mandatory

Default

backend-hostname

String

IP/hostname of one of the existing backend instances in the cluster

Existing backend IP/FQDN

Yes

client-hostname

String

IP/hostname of the client currently being added

Unique IP/FQDN

Yes

Note: On completion of this stage, the host-ID of the newly added host will be received. Make a note of it for the next steps.

Stage 3: Configuring the Host as Client

Command: weka 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=<frontend-dedicated-cores>

Parameters in Command Line

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 Weka 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 frontend-dedicated-cores must be equal

Yes, in order to configure a host as a client

Stage 4: Configuring Client Networking

Command: weka cluster host net add

Note: If the new client is to communicate with the Weka 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 Weka system cluster hosts:

weka cluster host net add <host-id> <device> --ips=<ips> --netmask=<netmask> --gateway=<gateway>

Parameters in Command Line

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 e.g., 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 ips (as described by netmask).

Not relevant for IB / L2 non-routable networks.

No

netmask

Number

Number of bits in the netmask, e.g., the netmask of 255.255.0.0 has 16 netmask bits

Describes the number of bits that identify a network ID (also known as CIDR).

No

Note: When configuring an InfiniBand client, do not pass the --ips, --netmask and --gateway parameters.

Note: InfiniBand/Ethernet clients can only join a cluster with the same network technology connectivity. It is possible to mix InfiniBand and Ethernet clients in the same cluster as long as the cluster backends are connected to both network technologies.

Stage 5: Applying the Host Configuration

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]

Parameters in Command Line

Name

Type

Value

Limitations

Mandatory

Default

host-id

Comma-separated string

Identifier of the host to be added to the cluster

Must be a valid host identifier

Yes

force

Boolean

Do not prompt for confirmation

No

Off

Verify that the Weka software is installed on the client host according to the installation instructions. For further information, see and

diskless-servers
Obtaining the Weka Install File
Mounting Filesystems Using the Stateless Clients Feature
Mounting Filesystems Using fstab
Mounting Filesystems Using autofs
Stage 1 in Weka System Installation Process.