docs: V2 data engine feature docs (RDMA transport, QoS limits, shallow/deep copy) and settings reference updates#1383
Open
jleeh wants to merge 1 commit into
Open
Conversation
jleeh
force-pushed
the
pr/docs/v2-feature-docs
branch
from
048fb75 to
5396300
Compare
✅ Deploy Preview for longhornio ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for longhornio ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
New feature pages: - RDMA Transport Support: auto-detected dual-listener TCP+RDMA, mixed clusters - Per-Engine QoS Limits: IOPS/bandwidth caps via SPDK bdev_set_qos_limit with usage guide - Shallow Copy and Deep Copy: efficient rebuild primitives, pipeline depth, range copy Updated settings reference: - Data Engine Replica Controller Loss Timeout (ctrlr_loss_timeout_sec) - Data Engine Replica Reconnect Delay (reconnect_delay_sec) - Data Engine Replica Fast I/O Fail Timeout (fast_io_fail_timeout_sec) - Data Engine Shallow Copy Pipeline Depth (shallow_copy_pipeline_depth) Updated v2-data-engine index page with links to new feature pages Signed-off-by: Jonny <jonny@linkpool.io>
jleeh
force-pushed
the
pr/docs/v2-feature-docs
branch
from
5396300 to
81b9e67
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This PR adds user-facing documentation for V2 data engine features and updates the settings reference with new V2 settings.
New feature pages
RDMA Transport Support (
v2-data-engine/rdma-transport.md)Documents the NVMe-oF RDMA transport support for the V2 data engine:
Per-Engine QoS Limits (
v2-data-engine/engine-qos.md)Documents per-volume QoS limits via SPDK
bdev_set_qos_limit:Shallow Copy and Deep Copy (
v2-data-engine/shallow-deep-copy.md)Documents the SPDK copy primitives used for v2 replica rebuilds:
Updated pages
Settings Reference (
references/settings.md)Added 4 new V2 data engine settings:
ctrlr_loss_timeout_sec) — timeout before a lost NVMe-oF controller is destructed. Supports-1(immediate failover),0(reconnect indefinitely), or positive value (seconds).reconnect_delay_sec) — delay between reconnection attempts to prevent tight retry loops.fast_io_fail_timeout_sec) — timeout after which I/O to a disconnected controller fails fast.shallow_copy_pipeline_depth) — pipeline depth for shallow copy during rebuilds (default 1 = sequential).V2 Data Engine Index (
v2-data-engine/_index.md)Updated with links to the 3 new feature pages and a brief overview of transport options and efficient rebuilds.
Related