[FEATURE] Local volume for distributed data workloads #3957
Closed
Description
Is your feature request related to a problem? Please describe
Longhorn is a highly available replica-based storage system, and it's good for fault tolerance, read performance, data protection, etc, but on the other side, it also needs some extra costs like requiring more disk paces for replication.
In some cases, especially for distributed data workloads (SS) like databases (ex: Cassandra, Kafka, etc), they already have their own data replication, sharding, etc, so we should provide a better volume type for these use cases but also still support existing specific volume functionalities like snapshotting, backup/restore, etc.
Describe the solution you'd like
- Extend Data Locality with
strict
orenforced
mode to require one replica should be local and next to the workload - Connecting the local replica via a local socket file instead of a TCP connection
Describe alternatives you've considered
N/A
Additional context
Metadata
Assignees
Labels
CSI related like control/node driver, sidecarsv1 data engine (iSCSI tgt)Longhorn instance manager (interface between control and data plane)Longhorn manager (control plane)Important feature/issue to highlightFeature request, new featureMust be implement or fixed in this release (managed by PO)Require updating the longhorn.io documentationRequire adding/updating enhancement proposal
Type
Projects
Status
Closed