Prerequisites and compatibility

This page describes the prerequisites and compatibility for the installation and upgrade 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 for more details.


  • Intel SandyBridge+ processors
  • AMD 2nd and 3rd Gen EPYC processors
Note: AES must be enabled in the BIOS


  • 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


Backends and Clients:

  • RHEL:
    • 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2
    • 8.6, 8.5, 8.4, 8.3, 8.2, 8.1, 8.0
  • CentOS:
    • 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2
    • 8.5, 8.4, 8.3, 8.2, 8.1, 8.0
  • Rocky Linux
    • 8.6
  • Ubuntu:
    • 18.04.6, 18.04.5, 18.04.4, 18.04.3, 18.04.2, 18.04.1, 18.04.0
    • 20.04.3, 20.04.2, 20.04.1, 20.04.0
  • Amazon Linux: 18.03, 17.09
  • Amazon Linux 2 LTS (formerly Amazon Linux 2 LTS 17.12)

Clients only:

  • SuSe:
    • 15 SP2
    • 12 SP5



  • 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 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).


  • 5.3-5.13
  • 4.4.0-1106 to 4.19
  • 3.10
Note: It is advisable to turn off auto kernel updates so it will not get upgraded to a yet unsupported version.

Weka installation directory

  • Directory: /opt/weka
  • Must be on an SSD or SSD-like performance, for example, M.2.
    • Cannot be shared remotely, NFS mounted, or on a 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 is available for the Weka system installation, with an additional 10 GB for each core used by Weka.
  • Use a separate filesystem on a separate partition for /opt/weka.


Note: At least 4k MTU is advised on Weka cluster hosts NICs, 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.



  • Amazon ENA
  • Broadcom 57810s 10GbE
  • Intel E810
  • Intel 40 Gbit (Beta)
  • Intel 10 Gbit
  • Mellanox ConnectX6-Dx
  • Mellanox ConnectX6-Lx
  • Mellanox ConnectX6
  • Mellanox ConnectX5
  • Mellanox ConnectX4
Intel E810 NIC requires the ice Linux Base Driver version 1.9.11 and firmware version 4.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. In addition, Intel E810 NIC only supports non-routed networks.

NIC drivers

Supported Mellanox OFED versions:
  • 5.6-
  • 5.6-
  • 5.4- (LTS)
  • 5.1-
  • 5.1-
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: 200 GbE / 100 GbE / 50GbE / 40 GbE / 25 GbE / 10 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.



  • Mellanox ConnectX6
  • Mellanox ConnectX5
  • Mellanox ConnectX4

NIC Drivers

Supported Mellanox OFED versions:
  • 5.6-
  • 5.6-
  • 5.4- (LTS)
  • 5.1-
  • 5.1-

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.



  • Support PLP (Power Loss Protection)
  • Dedicated for Weka system storage (partition not supported)
  • Supported drive capacity: Up to 128 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 must 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
    • S3 Standard
    • S3 Intelligent-Tiering
    • S3 Standard-IA
    • S3 One Zone-IA
    • S3 Glacier Instant Retrieval
  • Google Cloud Storage (GCS)
  • 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 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.) must support DPDK and SR-IOV VFs passthrough to the VM.
  • The hypervisor hosts and the client VMs must run the same OFED version.

For the VMWare platform:

  • If using vmxnet3 devices, do not enable the SR-IOV feature (which prevents vMotion). Each FrontEnd process requires a vmxnet3 device and IP, with an additional device and IP per client VM (for the 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.


  • 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)