Prerequisites and Compatibility

This page describes the prerequisites and compatibility for the installation of the Weka system.

The versions specified in the prerequisites and compatibility page apply to the latest minor version of the Weka system. See the relevant release notes in get.weka.io for more details.

CPU

• Intel SandyBridge+ processors

• AMD 2nd and 3rd Gen EPYC processors

Ensure the BIOS settings meet the following requirements:

• AES must be enabled.

• Secure Boot must be disabled.

Memory

• Enough memory to support the Weka system needs as described in memory requirements.

• More memory support for the OS kernel or any other application.

Operating System

Types

Backends and Clients:

• RHEL:

  • 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9

  • 8.0, 8.1, 8.2, 8.3, 8.4, 8.5, 8.6, 8.7

• CentOS:

  • 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9

  • 8.0, 8.1, 8.2, 8.3, 8.4, 8.5

• Rocky Linux:

  • 8.6, 8.7

• Ubuntu:

  • 18.04.0, 18.04.1, 18.04.2, 18.04.3, 18.04.4, 18.04.5

  • 20.04.0, 20.04.1

• Amazon Linux: 17.09, 18.03

• Amazon Linux 2 LTS (formerly Amazon Linux 2 LTS 17.12)

Clients Only:

• SuSe:

  • 12 SP5

  • 15 SP2

Configuration

General

• All Weka nodes must be synchronized in date/time (NTP recommended)

• A watchdog driver should be installed in /dev/watchdog (hardware watchdog recommended); search the Weka knowledge-base in the Weka support portal for more information and how-to articles
• If using mlocate or alike, it's advisable to exclude wekafs from updatedb filesystems lists; search the Weka knowledge-base in the Weka support portal for more information and how-to articles

SELinux

• SELinux is supported in both permissive and enforcing mode

  • targeted policy is supported

  • mls policy is not supported yet

Note: To set SELinux security context for files, -o acl should be used in the mount command, and wekafs should be defined to use extended-attributes in the SELinux policy configuration (fs_use_xattr).

Kernel

• 3.10

• 4.4.0-1106 to 4.19

• 5.3-5.4

Note: It is advisable to turn off auto kernel updates so it will not get upgraded to a yet unsupported version.

Weka Install Directory

• Directory: /opt/weka

• Should be on an SSD or SSD-like performance, e.g., M.2.

  • Cannot be shared remotely, NFS mounted or on RAM drive

• If there are two boot drives available, it is recommended to dedicate one for the OS and one for the Weka /opt/weka directory (there is no need to set software RAID, and some of its implementations are also known to have issues)

• At least 26 GB available for the Weka system installation, with an additional 10GB for each core used by Weka

• Use a separate filesystem on a separate partition for /opt/weka

Networking

Note: At least 4k MTU is advised on Weka cluster hosts NIC's, and the switches the hosts are connected to.

For both Ethernet and Infiniband configurations, a Weka system can be configured without jumbo frames. However, it will provide very limited performance and will not be able to handle high loads of data; please consult the Weka Sales or Support teams before running in this mode.

Jumbo Frames are not required for clients. However, performance might be limited.

Ethernet

NIC

• Amazon ENA

• Intel E810 2CQDA2

• Intel X540

• Intel X550-T1

• Intel X710

• Intel X710-DA2

• Intel XL710

• Intel XL710-Q2

• Intel XXV710

• Intel 82599ES

• Intel 82599

• Mellanox ConnectX-6-Lx

• Mellanox ConnectX-6-Dx

• Mellanox ConnectX-6

• Mellanox ConnectX-5-Ex

• Mellanox ConnectX-5-Bf

• Mellanox ConnectX-5

• Mellanox ConnectX-4-Lx

• Mellanox ConnectX-4

Intel E810 NIC has specific requirements and certain limitations:

• The ice Linux Base Driver version 1.9.11 and firmware version 4.0.0.

• Working with this NIC is only supported on RHEL 8.6 and Rocky Linux 8.6. For other operating systems, contact the Customer Success Team.
• Only non-routed network is supported with this NIC.

Note: LACP (link aggregation, also known as bond interfaces) is currently supported between ports on a single Mellanox NIC and is not supported when using VFs (virtual functions).

NIC Drivers

Supported Mellanox OFED versions:

• 5.1-2.5.8.0

• 5.1-2.6.2.0

• 5.4-3.4.0.0

• 5.6-1.0.3.3

• 5.6-2.0.9.0

• 5.8-1.1.2.1 LTS

Supported ENA drivers:

• 1.0.2 - 2.0.2

• A current driver from an official OS repository is recommended

Supported ixgbevf drivers:

• 3.2.2 - 4.1.2

• A current driver from an official OS repository is recommended

Supported Intel 40 drivers:

• 3.0.1-k - 4.1.0

• A current driver from an official OS repository is recommended

Supported ice drivers:

• 1.9.11

Ethernet Configuration

• Ethernet speeds: 10 GbE / 25 GbE / 40 GbE / 50GbE / 100 GbE / 200 GbE

• NICs bonding: Can bond dual ports on the same NIC (modes 1 or 4)

• VLAN: Not supported

• Connectivity between hosts: Ports 14000-14100

• Mellanox NICs:

  • One Weka system IP address for management and data plane

• Other vendors NICs

  • Weka system management IP address: One IP per server (configured prior to Weka installation)

  • Weka system data plane IP address: One IP address for each Weka core in each server (Weka will apply these IPs during the cluster initialization)
  • Weka system management IP: Ability to communicate with all Weka system data plane IPs

  • Virtual Functions (VFs): The maximum number of virtual functions supported by the device must be bigger than the number of physical cores on the host; you should set the number of VFs to the number of cores you wish to dedicate to Weka; some configuration may be required in the BIOS
  • SR-IOV: Enabled in BIOS

Note: When assigning a network device to the Weka system, no other application can create virtual functions (VFs) on that device.

InfiniBand

NIC

• Mellanox ConnectX4

• Mellanox ConnectX5

• Mellanox ConnectX6

NIC Drivers

Supported Mellanox OFED versions:

• 5.1-2.5.8.0

• 5.1-2.6.2.0

• 5.4-3.4.0.0

• 5.6-1.0.3.3

• 5.6-2.0.9.0

• 5.8-1.1.2.1 LTS

Infiniband Configuration

• InfiniBand speeds: FDR / EDR / HDR

• Subnet manager: Configured to 4092

• One Weka system IP address for management and data plane

• PKEYs: Supported

• Dual InfiniBand can be used for both HA and higher bandwidth

Note: If it is necessary to change PKEYs, contact the Customer Success Team.

HA

• Network configured as described in Weka Networking - HA.

SSDs

• Support PLP (Power Loss Protection)

• Dedicated for Weka system storage (partition not supported)

• Supported drive capacity: Up to 17 TiB

• IOMMU mode for SSD drives is not supported; When IOMMU configuration is required on the Weka cluster servers (e.g., due to specific applications when running the Weka cluster in converged mode), contact the Weka support team.

Note: To get the best performance, make sure TRIM is supported by the device and enabled in the operating system.

Object Store

• API should be S3 compatible:

  • GET

    • Including byte-range support with expected performance gain when fetching partial objects

  • PUT

    • Supports any byte size of up to 65 MiB

  • DELETE

• Data Consistency: AWS S3 consistency guarantee:

  • GET after single PUT should be fully consistent

  • Multiple PUTs should be eventually consistent

Certified Object Stores:

• AWS S3

• Cloudian HyperStore (version 7.3 and up)

• Dell EMC ECS v3.5 and up

• HCP Classic V9.2 and up (with versioned buckets only)

• HCP for Cloud Scale V2.x

• IBM Cloud Object Storage System (version 3.14.7 and up)

• Quantum ActiveScale (version 5.5.1 and up)

• Red Hat Ceph Storage (version 5.0 and up)

• Scality (version 7.4.4.8 and up)

• SwiftStack (version 6.30 and up)

Virtual Machines

VMs can be used as clients only, assuming they meet the following prerequisite:

For UDP clients:

• To avoid irregularities, crashes, and inability to handle application load, make sure there is no CPU starvation to the Weka process by both reserving the CPU in the virtual platform and dedicating a core to the Weka client.

• The root filesystem should handle a 3K IOPS load by the Weka client.

For DPDK clients (on top of the UDP requirements):

• The virtual platform interoperability (hypervisor, NICs, CPUs, different versions, etc.) should support DPDK and SR-IOV VFs passthrough to the VM.

• The hypervisor hosts and the client VMs should run the same OFED version.

For VMWare platform:

• Instead of using SR-IOV (which prevents vMotion), it is possible to use vmxnet3 devices. Each FrontEnd process will require a vmxnet3 device and IP, with an additional device and IP per client VM (for management process).

• Using vmxnet3 is only supported with core dedication.

For additional information and how-to articles, search the Weka knowledgebase in the Weka support portal or contact the Weka support team.

KMS

• HashiCorp Vault (version 1.1.5 up to 1.9.x)
• KMIP compliant KMS (protocol version 1.2 and up)

  • The KMS should support encryption-as-a-service (KMIP encrypt/decrypt APIs)

  • KMIP certification has been conducted with Equinix SmartKey (powered by Fortanix KMS)