Skip to content

feat(chart): add default-nvme-tcp-nr-io-queues setting docs for v1.13.0 and v1.12.2 #1424

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.

Sign up for GitHub

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

Merged
derekbit merged 1 commit into from
Aug 18, 2026
+14 −0
Merged

feat(chart): add default-nvme-tcp-nr-io-queues setting docs for v1.13.0 and v1.12.2 #1424

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions content/docs/1.12.2/references/settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,7 @@ weight: 1
- [Data Engine Log Flags](#data-engine-log-flags)
- [Replica Rebuilding Bandwidth Limit](#replica-rebuilding-bandwidth-limit)
- [Manager URL](#manager-url)
- [Default NVMe-TCP Number Of IO Queues](#default-nvme-tcp-number-of-io-queues)
- [Default Ublk Queue Depth](#default-ublk-queue-depth)
- [Default Ublk Number Of Queue](#default-ublk-number-of-queue)
- [Node Disk Health Monitoring](#node-disk-health-monitoring)
Expand Down Expand Up @@ -651,6 +652,12 @@ This setting is useful when accessing the Longhorn API through Ingress or Gatewa

For more details, see [Manager URL for External API Access](../../important-notes/#manager-url-for-external-api-access).

#### Default NVMe-TCP Number Of IO Queues

> Default: `{"v2":"0"}`

The default number of I/O queues the kernel initiator creates when connecting a volume frontend over NVMe-TCP. This caps the per-volume in-flight commands to the number of I/O queues multiplied by the negotiated queue size (128). This setting applies to volumes using the V2 Data Engine with the block device frontend and takes effect on (re)attach. The value can be overridden per volume using volume.spec.nvmeTcpNrIoQueues. 0 means unspecified (kernel default, one queue per online core).

#### Default Ublk Queue Depth

> Default: `{"v2":"128"}`
Expand Down
7 changes: 7 additions & 0 deletions content/docs/1.13.0/references/settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,7 @@ weight: 1
- [Data Engine Log Flags](#data-engine-log-flags)
- [Replica Rebuilding Bandwidth Limit](#replica-rebuilding-bandwidth-limit)
- [Manager URL](#manager-url)
- [Default NVMe-TCP Number Of IO Queues](#default-nvme-tcp-number-of-io-queues)
- [Default Ublk Queue Depth](#default-ublk-queue-depth)
- [Default Ublk Number Of Queue](#default-ublk-number-of-queue)
- [Node Disk Health Monitoring](#node-disk-health-monitoring)
Expand Down Expand Up @@ -670,6 +671,12 @@ This setting is useful when accessing the Longhorn API through Ingress or Gatewa

For more details, see [Manager URL for External API Access](../../important-notes/#manager-url-for-external-api-access).

#### Default NVMe-TCP Number Of IO Queues

> Default: `{"v2":"0"}`

This setting defines the default number of I/O queues the kernel initiator creates when connecting a volume frontend over NVMe-TCP. It caps the in-flight commands per volume to the number of I/O queues multiplied by the negotiated queue size (128). This applies to volumes using the V2 Data Engine with the block device frontend, and changes take effect upon volume attachment or reattachment. You can override this value on a per-volume basis using `volume.spec.nvmeTcpNrIoQueues`. 0 means unspecified (kernel default, one queue per online core).

#### Default Ublk Queue Depth

> Default: `{"v2":"128"}`
Expand Down
Loading