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). See List of statistics.
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.
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.
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).