Add GPU vector indexing monitoring to _xpack/usage (#141932)#142660
Merged
elasticsearchmachine merged 2 commits intoelastic:9.3from Feb 18, 2026
Merged
Add GPU vector indexing monitoring to _xpack/usage (#141932)#142660elasticsearchmachine merged 2 commits intoelastic:9.3from
elasticsearchmachine merged 2 commits intoelastic:9.3from
Conversation
Expose GPU vector indexing usage via the _xpack/usage and _xpack APIs
GET _xpack response (features section):
```json
{
"gpu_vector_indexing": {
"available": true,
"enabled": true
}
}
```
_xpack field semantics (local node only): - available: License permits
GPU indexing - enabled: the node handling this request has GPU hardware
and hasn't disabled it via vectors.indexing.use_gpu=false
GET _xpack/usage response:
```json
{
"gpu_vector_indexing": {
"available": true,
"enabled": true,
"index_build_count": 30,
"nodes_with_gpu": 3,
"nodes": [
{ "type": "NVIDIA L4", "memory_in_bytes": 24000000000,
"enabled": true, "index_build_count": 10 },
{ "type": "NVIDIA L4", "memory_in_bytes": 24000000000,
"enabled": true, "index_build_count": 10 },
{ "type": "NVIDIA A100", "memory_in_bytes": 80000000000,
"enabled": true, "index_build_count": 10 }
]
}
}
```
_xpack/usage field semantics (cluster-wide): - available: License
permits GPU indexing - enabled: at least one node has configured GPU
hardware and hasn't disabled it via vectors.indexing.use_gpu=false -
index_build_count: total GPU index builds across cluster -
nodes_with_gpu: count of data nodes with GPU support - nodes[]: per-node
GPU details (type, memory, enabled, build count)
Backport for elastic#141932
mayya-sharipova
added a commit
to mayya-sharipova/elasticsearch-specification
that referenced
this pull request
Feb 24, 2026
Adds specification for the gpu_vector_indexing feature introduced in elastic/elasticsearch#142660.
This was referenced Feb 24, 2026
pquentin
added a commit
to elastic/elasticsearch-specification
that referenced
this pull request
Feb 25, 2026
* Add GPU vector indexing to xpack info and usage Adds specification for the gpu_vector_indexing feature introduced in elastic/elasticsearch#142660. * Update specification/xpack/usage/types.ts Co-authored-by: Quentin Pradet <quentin.pradet@gmail.com> * Update specification/xpack/usage/types.ts Co-authored-by: Quentin Pradet <quentin.pradet@gmail.com> --------- Co-authored-by: Quentin Pradet <quentin.pradet@gmail.com>
github-actions bot
pushed a commit
to elastic/elasticsearch-specification
that referenced
this pull request
Feb 25, 2026
* Add GPU vector indexing to xpack info and usage Adds specification for the gpu_vector_indexing feature introduced in elastic/elasticsearch#142660. * Update specification/xpack/usage/types.ts Co-authored-by: Quentin Pradet <quentin.pradet@gmail.com> * Update specification/xpack/usage/types.ts Co-authored-by: Quentin Pradet <quentin.pradet@gmail.com> --------- Co-authored-by: Quentin Pradet <quentin.pradet@gmail.com> (cherry picked from commit cfd9082)
mayya-sharipova
added a commit
to elastic/elasticsearch-specification
that referenced
this pull request
Feb 25, 2026
Adds specification for the gpu_vector_indexing feature introduced in elastic/elasticsearch#142660. Co-authored-by: Mayya Sharipova <mayya.sharipova@elastic.co> Co-authored-by: Quentin Pradet <quentin.pradet@gmail.com>
mayya-sharipova
added a commit
to mayya-sharipova/elasticsearch
that referenced
this pull request
Mar 3, 2026
PR elastic#142660 introduced a bug where NodeGpuStatsResponse uses writeVLong to serialize totalGpuMemoryInBytes, which is -1 when no GPU is present. This causes repeated WARN log flooding from OutboundHandler on multi-node clusters with non-GPU nodes. The bug was resolved in elastic#142991 for 9.3.2. Adds known issue docs with a mitigation (raising OutboundHandler log level to ERROR).
mayya-sharipova
added a commit
that referenced
this pull request
Mar 3, 2026
PR #142660 introduced a bug where NodeGpuStatsResponse uses writeVLong to serialize totalGpuMemoryInBytes, which is -1 when no GPU is present. This causes repeated WARN log flooding from OutboundHandler on multi-node clusters with non-GPU nodes. The bug was resolved in #142991 for 9.3.2. Adds known issue docs with a mitigation (raising OutboundHandler log level to ERROR).
shmuelhanoch
pushed a commit
to shmuelhanoch/elasticsearch
that referenced
this pull request
Mar 4, 2026
PR elastic#142660 introduced a bug where NodeGpuStatsResponse uses writeVLong to serialize totalGpuMemoryInBytes, which is -1 when no GPU is present. This causes repeated WARN log flooding from OutboundHandler on multi-node clusters with non-GPU nodes. The bug was resolved in elastic#142991 for 9.3.2. Adds known issue docs with a mitigation (raising OutboundHandler log level to ERROR).
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
2 participants
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.
Expose GPU vector indexing usage via the _xpack/usage and _xpack APIs
GET _xpack response (features section):
{ "gpu_vector_indexing": { "available": true, "enabled": true } }_xpack field semantics (local node only): - available: License permits GPU indexing - enabled: the node handling this request has GPU hardware and hasn't disabled it via vectors.indexing.use_gpu=false
GET _xpack/usage response:
{ "gpu_vector_indexing": { "available": true, "enabled": true, "index_build_count": 30, "nodes_with_gpu": 3, "nodes": [ { "type": "NVIDIA L4", "memory_in_bytes": 24000000000, "enabled": true, "index_build_count": 10 }, { "type": "NVIDIA L4", "memory_in_bytes": 24000000000, "enabled": true, "index_build_count": 10 }, { "type": "NVIDIA A100", "memory_in_bytes": 80000000000, "enabled": true, "index_build_count": 10 } ] } }_xpack/usage field semantics (cluster-wide): - available: License permits GPU indexing - enabled: at least one node has configured GPU hardware and hasn't disabled it via vectors.indexing.use_gpu=false - index_build_count: total GPU index builds across cluster - nodes_with_gpu: count of data nodes with GPU support - nodes[]: per-node GPU details (type, memory, enabled, build count)
Backport for #141932