Allow configuring dedicated volume for ScyllaDB commit log #2086
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
What should the feature do?
While using the helm chart to deploy a cluster, it is currently impossible to use a separate volume for the commitlog, which is a pretty common operation (and highly recommended when using high latency volumes, such as spinning disks).
racks[].storage
currently only specifies one volume, which is where both data and commitlog will live, and ideally we would be able to specify another (optional) key for the commitlog,such as
racks[].commitlogStorage
, or subdivide the existing key intoracks[].storage.data
andracks[].storage.commitlog
.racks[].volumes
cannot be used for this purpose because it will mount the volume to the entire rack, and not one per individual node.What is the use case behind this feature?
Separating the commitlog and data directories into different volumes is required if you wish to have acceptable performance while using spinning disks, and also can be an important strategy to maximize throughput while using networked storage such as EBS.
Since it is hard/impossible to use local disks with helm/k8s, this option should be readily available since the vast majority of users will be using networked storage, and separating the commitlog can greatly improve the cluster performance.
Anything else we need to know?
Briefly discussed on slack:
https://scylladb-users.slack.com/archives/CFFVC7EA0/p1723831259255499
The text was updated successfully, but these errors were encountered: