Skip to content

[FEATURE] Local volume for distributed data workloads #3957

Closed
@innobead

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 or enforced 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

#1965

Metadata

Labels

area/csiCSI related like control/node driver, sidecarsarea/v1-data-enginev1 data engine (iSCSI tgt)component/longhorn-instance-managerLonghorn instance manager (interface between control and data plane)component/longhorn-managerLonghorn manager (control plane)highlightImportant feature/issue to highlightkind/featureFeature request, new featurepriority/0Must be implement or fixed in this release (managed by PO)require/docRequire updating the longhorn.io documentationrequire/lepRequire adding/updating enhancement proposal

Type

No type

Projects

  • Status

    Closed

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions