Skip to content

CCL-2382: add io_uring to storage performance config - #300

Closed
lakhansamani wants to merge 1 commit into
mainfrom
feat/lakhan/ccl-2382-io-uring
Closed

lakhansamani wants to merge 1 commit into
mainfrom
feat/lakhan/ccl-2382-io-uring

Conversation

@lakhansamani

Copy link
Copy Markdown

Ticket: CCL-2382

Summary
Adds database_configuration.storage.performance.io_uring. It is hybrid cloud
only: a managed cluster ignores it and, from Qdrant v1.20.0, gets auto from
Qdrant Cloud. async_scorer stays settable and only gains that note in its
description — no Deprecated marker, which would also warn hybrid users.

Two deviations from the spec, both deliberate:

  • The accepted values are the proto enum names
    (DATABASE_CONFIGURATION_IO_URING_MODE_AUTO / ..._DISABLED), not
    auto/disabled. Every other enum in this provider is exposed that way
    (gpu_type, rebalance_strategy, log_level), and the flatten path uses
    .String(). Say the word if the friendlier spelling is wanted instead.
  • Docs are not regenerated yet, see below.

Blocked, and not only on qdrant/qdrant-cloud-public-api#538. The pin here is
v0.201.0, and anything new enough to carry the io_uring enum also carries
qdrant/qdrant-cloud-public-api#519, which dropped SpaceEndpoint.rest_port and
grpc_port. qdrant/schemas_serverless_space.go still reads both, so the
build fails there until the provider absorbs SVL-97 — a separate decision,
since those two fields are in the provider's public schema. tfplugindocs
needs a working build, so docs regeneration waits on the same thing.

Tests
New TestStoragePerformanceIOUringRoundTrip: expand -> proto -> flatten keeps
the mode, an unset mode stays absent instead of being sent as "", and the
schema validates only the enum names while staying Optional + Computed.

go test ./qdrant/ — the cluster tests pass, verified by stubbing the two
serverless lines above locally; those stubs are not in this branch, so CI is
red until SVL-97 is handled.

Hybrid cloud only: a managed cluster ignores it and, from Qdrant v1.20.0,
gets auto from Qdrant Cloud. async_scorer keeps working, so no Deprecated
marker that would also warn hybrid users.
@lakhansamani

lakhansamani commented Oct 20, 2026 •

Copy link
Copy Markdown
Author

Closing: CCL-2382 no longer exposes io_uring through the API.

Qdrant checks for itself whether io_uring is available, so there is nothing to
configure per cluster from the cloud side and no managed-cluster default to
render. async_scorer stays configurable exactly as it is today — this branch's
changes to it are dropped with the rest.

What remains of the ticket is the CRD field in qdrant/kubernetes-api#327 plus the
operator pass-through, so the setting can still be overridden per cluster with a
QdrantCluster spec patch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant