Add 9.3.1 known issue for GPU stats bug#143523
Conversation
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).
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
🔍 Preview links for changed docs |
ℹ️ Important: Docs version tagging👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version. We use applies_to tags to mark version-specific features and changes. Expand for a quick overviewWhen to use applies_to tags:✅ At the page level to indicate which products/deployments the content applies to (mandatory) What NOT to do:❌ Don't remove or replace information that applies to an older version 🤔 Need help?
|
kilfoyle
left a comment
There was a problem hiding this comment.
LGTM! 🚀 Thanks @mayya-sharipova!
|
@mayya-sharipova @kilfoyle does this need to be backported ? Or are docs always served from main? |
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).
Thanks for checking @benwtrent! In the 9.x docs everything is served from |
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).