The Weka agent is software installed on user application servers that need access to the Weka file services. When using the Stateless Client feature, the agent is responsible for ensuring that the correct client software version is installed (depending on the cluster version) and that the client connects to the correct cluster.
A host that runs the Weka software and can also be installed with SSD drives dedicated to the Weka system, providing services to client hosts.
The Weka client is software installed on user application servers that need access to the Weka file services. The Weka client implements a kernel-based filesystem driver and the logic and networking stack to connect to the Weka backend hosts and be part of a cluster.
A collection of Weka backends, together with Weka clients installed on the application servers, forming one sharable, distributed and scalable file storage system.
The target period of time for tiered data to be retained on an SSD.
The number of data blocks in each logical data protection group.
Basic Weka configuration involving the creation of a cluster by dedicating complete servers to Weka backends, as opposed to converged deployment.
A collection of hardware components that can fail together due to a single root cause.
A collection of filesystems which share a common connectivity to an object store system.
Frequently-used data (as opposed to warm data), usually residing on SSDs.
The configuration of Weka backends running on the same host with other applications.
Amount of space available for user data on SSDs in a configured Weka system.
The total capacity assigned to filesystems. This includes both SSD and object store capacity.
The Weka process of rehydrating data from an object store to an SSD, based on a prediction of future data access.
Total SSD capacity owned by the user.
Target time for data to be stored on SSDs before release from the SSDs to an object store.
The deletion of the SSD copy of data which has been tiered to the object store.
The creation of an SSD copy of data stored on object store only.
A mode of the Weka software which has been installed and is running, but has not been attached to a cluster.
A Weka feature for uploading snapshots to object stores.
Weka configuration consisting of SSDs and object stores for data storage.
Copying of data to an object store, while it still remains on the SSD.
The minimum time to wait before considering data for tiering from an SSD to an object store.
The storage capacity available for new filesystems.
Less frequently-used data (as opposed to hot data), usually residing on an object store.