Fix serialization of NodeGpuStatsResponse when no GPU is present (#142937)#142991
Merged
elasticsearchmachine merged 1 commit intoelastic:9.3from Feb 24, 2026
Merged
Conversation
…stic#142937) NodeGpuStatsResponse uses writeVLong for totalGpuMemoryInBytes, which throws IllegalStateException on the sentinel value -1 returned by GPUSupport.getTotalGpuMemory() when no compatible GPU is available. The fix is to replace -1 with 0L (which does not change the semantics), and add a serialization round-trip test that reproduces the original failure and validates fix. resolves elastic#142936
mayya-sharipova
added a commit
to mayya-sharipova/elasticsearch
that referenced
this pull request
Mar 3, 2026
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
to mayya-sharipova/elasticsearch
that referenced
this pull request
Mar 3, 2026
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
to mayya-sharipova/elasticsearch
that referenced
this pull request
Mar 3, 2026
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
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
3 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.
NodeGpuStatsResponse uses writeVLong for totalGpuMemoryInBytes, which throws IllegalStateException on the sentinel value -1 returned by GPUSupport.getTotalGpuMemory() when no compatible GPU is available. The fix is to replace -1 with 0L (which does not change the semantics), and add a serialization round-trip test that reproduces the original failure and validates fix.
resolves #142936
Backport for #142937