Skip to content

docs: clarify AvailableNodeIndexes are not contiguous 0..Size-1 #281

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
syndbg merged 1 commit into from
Jun 11, 2026
Merged

docs: clarify AvailableNodeIndexes are not contiguous 0..Size-1 #281

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
8 changes: 8 additions & 0 deletions api/v1/qdrantcluster_types.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -994,6 +994,14 @@ type QdrantClusterStatus struct {
AvailableNodes int `json:"availableNodes,omitempty"`
// AvailableNodeIndexes specifies the indexes of the individual nodes in the cluster
// The number of indexes should be equal with the AvailableNodes field.
// NOTE: these indexes are NOT guaranteed to be the contiguous range 0..Size-1.
// New indexes are allocated monotonically (always above the current maximum) and are
// never re-compacted, so after repeated scale-up-then-scale-down rounds (e.g.
// on-demand-replication-restart or version upgrades) the indexes - and the per-index
// pod names and PVCs - can grow well beyond Spec.Size. This is expected behavior:
// indexes are reserved-not-reused to avoid colliding with not-yet-reclaimed PVCs/PVs
// and lingering consensus peers from a prior occupant of the same index. Consumers
// must treat this slice as the source of truth and must not assume contiguous ordinals.
// +optional
AvailableNodeIndexes []int `json:"availableNodeIndexes,omitempty"`
// DeleteInProgessNodeIndexes specifies the indexes of the nodes in the cluster which are in progress of deleting and required to be deleted.
Expand Down
8 changes: 8 additions & 0 deletions charts/qdrant-kubernetes-api/templates/region-crds/qdrant.io_qdrantclusters.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3455,6 +3455,14 @@ spec:
description: |-
AvailableNodeIndexes specifies the indexes of the individual nodes in the cluster
The number of indexes should be equal with the AvailableNodes field.
NOTE: these indexes are NOT guaranteed to be the contiguous range 0..Size-1.
New indexes are allocated monotonically (always above the current maximum) and are
never re-compacted, so after repeated scale-up-then-scale-down rounds (e.g.
on-demand-replication-restart or version upgrades) the indexes - and the per-index
pod names and PVCs - can grow well beyond Spec.Size. This is expected behavior:
indexes are reserved-not-reused to avoid colliding with not-yet-reclaimed PVCs/PVs
and lingering consensus peers from a prior occupant of the same index. Consumers
must treat this slice as the source of truth and must not assume contiguous ordinals.
items:
type: integer
type: array
Expand Down
8 changes: 8 additions & 0 deletions crds/qdrant.io_qdrantclusters.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3454,6 +3454,14 @@ spec:
description: |-
AvailableNodeIndexes specifies the indexes of the individual nodes in the cluster
The number of indexes should be equal with the AvailableNodes field.
NOTE: these indexes are NOT guaranteed to be the contiguous range 0..Size-1.
New indexes are allocated monotonically (always above the current maximum) and are
never re-compacted, so after repeated scale-up-then-scale-down rounds (e.g.
on-demand-replication-restart or version upgrades) the indexes - and the per-index
pod names and PVCs - can grow well beyond Spec.Size. This is expected behavior:
indexes are reserved-not-reused to avoid colliding with not-yet-reclaimed PVCs/PVs
and lingering consensus peers from a prior occupant of the same index. Consumers
must treat this slice as the source of truth and must not assume contiguous ordinals.
items:
type: integer
type: array
Expand Down
Loading