Add known issue for upgrading to 9.2.4#140738
Conversation
Backports for elastic#139910 were released in different releases, causing some upgrade paths to be broken. This commit adds a note about a failure that can occur between 9.1.10 and 9.2.4.
rjernst
added
>docs
elasticsearchmachine
added
v9.4.0
Team:Core/Infra
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
|
Pinging @elastic/core-docs (Team:Docs) |
docs/release-notes/known-issues.md
Outdated
|
|
||
| * Upgrading from 9.1.10 to 9.2.4 may cause the following error: | ||
|
|
||
| ```org.elasticsearch.xcontent.XContentParseException: [-1:107008] [node_shutdown_info] unknown field [shutdown_started_millis] did you mean [shutdown_startedmillis]``` |
There was a problem hiding this comment.
Wondering, should it mention the exception that bubbles up from this? Might be easy to miss above far down the stack trace
fatal exception while booting Elasticsearch org.elasticsearch.ElasticsearchException: failed to load metadata at org.elasticsearch.gateway.GatewayMetaState.start(GatewayMetaState.java:119) ~[elasticsearch-9.2.4.jar:?] at [..] Caused by: org.elasticsearch.gateway.CorruptStateException: org.elasticsearch.xcontent.XContentParseException: [-1:107032] [node_shutdown] failed to parse field [nodes]
|
@mosche @leemthompo I added additional context and made the example a block as suggested. |
🔍 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?
|
Backports for elastic#139910 were released in different releases, causing some upgrade paths to be broken. This commit adds a note about a failure that can occur between 9.1.10 and 9.2.4.
5 participants
Backports for #139910 were released in different releases, causing some upgrade paths to be broken. This commit adds a note about a failure that can occur between 9.1.10 and 9.2.4.