Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lep: add local-volume #4928
lep: add local-volume #4928
Changes from all commits
1428be7
000e70e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Local Volume
Summary
Longhorn can support local volume to provide better IO latencies and IOPS.
Related Issues
#3957
Motivation
Goals
Non-goals
Proposal
strict-local
data locality.best-effort
data locality, the engine and replica of a local volume have to be located on the same node.User Stories
Longhorn is a highly available replica-based storage system. As the data path is designed for the replication, a volume with a single replica still suffers from high IO latency. In some cases, the distributed data workloads such as databases already have their own data replication, sharding, etc, so we should provide a volume type for these use cases while supporting existing volume functionalities like snapshotting, backup/restore, etc.
User Experience In Detail
disabled
andbest-effort
data localities will not be changed.strict-local
data localitydisabled
orbest-effort
data locality when the volume is not detacheddisabled
orbest-effort
data locality when the volume is detachedCLI Changes
--volume-name
in engine-binaryreplica
command/var/lib/longhorn/unix-domain-socket/${volume name}.sock
--data-server-protocol
in engine-binaryreplica
commandtcp
(default) andunix
--data-server-protocol
in engine-binarycontroller
commandtcp
(default) andunix
Design
Implementation Overview
CRDs
strict-local
involume.Spec.DataLocality
Volume Creation and Attachment
strict-local
data locality, the replica is scheduled on the node where the engine is located.--volume-name ${volume name}
and--data-server-protocol unix
./var/lib/longhorn/unix-domain-socket/${volume name}.sock
).--data-server-protocol unix
.Validating Webhook
strict-local
data locality, thenumberOfReplicas
should be 1.strict-local
and other data localities is not allowable.Test Plan
Integration tests
numberOfReplicas=1
anddataLocality=strict-local
.dataLocality=strict-local
butnumberOfReplicas>1
numberOfReplicas
to a value greater than onedataLocality
todisabled
orbest-effort