Documentation revision history

WEKA version	Description of changes
4.4.0	This release includes a variety of optimizations to benefit customers operating the WEKA Data Platform at scale. Improvements weka stats performance enhancements reduce the latency of metric reporting, especially on large clusters. To limit access to POSIX filesystems in Organizations, define access lists by network and role by weka security policy hierarchy. Attach, detach, and test policies by weka org security policy. Customers using clients with multiple clusters can now store profile tokens and reference them by name for convenience. The profile token location is $HOME/.weka/auth-token-<profile>.json, and invocation by the new profile parameter, such as weka user login [—-profile <profile-name>]. See Manage authentication across multiple clusters with connection profiles SMB-W enhancements WEKA now supports configuring shares with user permissions in advance of validating the user with directory services Commands share add and share update now support allow-guest-access. Added the ACLs feature to enable or disable Windows Access-Control Lists for the share, offering options for POSIX, Windows, or Hybrid (default: POSIX) and allowing interoperability by prioritizing the most recent permission based on timestamps. S3 enhancement Introduced an updated health-check URL, /wekas3api/health/ready, for load balancers to use in assessing the health of S3 servers, improving monitoring and load balancing capabilities. Additional enhancements WEKA client support is extended to: Debian 10, Rocky 8.6, Rocky 8.7, Rocky 8.8, Oracle Linux 9, and SLES 15 SP5. Added a verification step for LLQ and WC in the upgrade workflow. To ensure proper LLQ functionality after upgrades, verify that Write Combining (WC) is enabled in the igb_uio driver. See 5. Verify LLQ and WC are enabled in AWS. Added a CLI reference guide, which is generated from the output of running the weka command with the help option. It provides detailed descriptions of available commands, arguments, and options. See CLI reference guide.
	Added the WEKApod Data Platform Appliance Guide, which provides comprehensive instructions for setting up and configuring the WEKApod™. The WEKApod is a turnkey data platform appliance designed as a high-performance datastore for NVIDIA DGX SuperPOD. Each appliance includes pre-configured storage servers and software, enabling simplified deployment and faster time to value. For details, see https://github.com/weka/docs-weka-io/blob/4.4/readme/broken-reference/README.md.
4.3.5	This release aims to enhance usability, focusing on WEKA SMB-W. It also contains field fixes and support for new platforms and hardware. SMB-W enhancements Case sensitivity in SMB-W shares, beyond the case insensitive limits of the Microsoft implementation. Symbolic link following in SMB-W shares. Named streams support in shares, sometimes called alternate data streams (ADS). Optional reduction of shared state between SMB-W containers for workloads that don't rely on it. Zero copy support for MacOS clients is enabled by default, but can be disabled in share options. Share updates support read-only and hidden properties. S3 enhancements Updated the s3 cluster status output to align with the style of weka cluster container, showing details like Hostname, Status, Uptime, Last Error, and Active Requests. Use weka s3 cluster status-old during upgrades, as initial output may be inaccurate until all frontend containers are updated. Additional enhancements The REST API for quota listing includes the full directory path, aligning with the CLI command output. Extended support for operating systems: Clients: RHEL/Rocky Linux 9.4, AlmaLinux 9.4, 8.10, Debian 12. Backends: RHEL/Rocky Linux 9.4. Improved NFS read operation performance. Added support for Broadcom P2200. Added support for colored output in the weka status and other table-returning commands, configurable by the --color option or WEKA_CLI_COLOR environment variable. See WEKA CLI command output colors. Introduced the Data Services container for running resource-intensive background tasks, starting with the Quota Coloring task, with more tasks to be supported in future releases. See Set up a Data Services container for background tasks.
4.3.4	This release contains an important enhancement for clusters under extreme memory pressure.
N/A	Added a new topic to WEKA and Slurm integration: Avoid conflicting CPU allocations.
4.3.3	NFS locking is fully supported for protocol versions 3 and 4, and configurable through global parameters. Added support for additional QLC drives for higher density deployments while maintaining high performance and longevity standards. SMB-W performance is optimized for macOS clients. SMB-W share access now supports allow and deny statements based on IP address. For Windows clients with many top-level entities, folder options appear without delay. WEKA client support extended to Rocky 8.10, Rocky 8.9, Rocky 9.3, and Oracle Linux 9. WEKA backend support extended to Rocky 8.10.
4.3.2	Added graceful container management to ensure safe stopping or restarting of a container. See Graceful container management: ensuring safe actions. Added the WEKA Cloud Deployment Manager (CDM) User Guide, simplifying the deployment of WEKA clusters in public cloud environments (including AWS, Azure, and GCP). A new algorithm for multi-part uploads is now the default, decreasing resource overhead for most customers using WEKA S3. WEKA S3 response codes are now in weka stats, with types and categories listed under Operation (Envoy). WEKA S3 logs now report real remote client addresses via the X-Forwarded-For header. The default memory limit for SMB-W containers has been raised to 32GB to accommodate trends in customer requirements related to SMB protocol performance. Deprecation RHEL 7 and CentOS 7 support have reached EOL status. Deployment on Amazon EC2 instance families M4, R3, R4, and C4 are no longer supported.
4.3.1	Added a topic to restrict a stateless client’s operations to only the essential APIs for mounting and unmounting operations. See Isolated port for restricted stateless client operations. Added the following instance types to the Client EC2 instances section: C7a, M7i, R7a, X2idn, X2iedn, R7iz, R7g, R7gd, R6g, R6gd, G6, GR6, F1, and Z1d.
4.3.0	Initial support for ARM, specifically for ARM-based EC2 instances in AWS. To reflect the instruction set architecture of hosts in a cluster, APIs, and commands like the Weka cluster server list now contain an architecture column. Added NFS integration with Kerberos service. Synchronized snapshots have been re-enabled. A new --client-only flag in the weka version get and weka version set commands. When used, this flag ensures that only components necessary for stateless clients are considered for installation. Discontinued support for Intel processor families SandyBridge (2011) and IvyBridge (2012). Discontinued support for the legacy NFS stack in 4.3.0. If legacy NFS is enabled, upgrading to 4.3.0 will fail. weka alerts command output update The muted column is removed from the weka alerts command output unless --muted or -v is provided. weka nfs interface-group add command update The manage-gids parameter, which was always set to true, has been eliminated from the weka nfs interface-group add command and associated API. weka fs tier s3 command output update The following columns have been removed from the weka fs tier s3 command output: NODES UP, NODES DOWN, and NODES UNKNOWN. Instead, more detailed columns have been added in the verbose output (using -v).