-
Notifications
You must be signed in to change notification settings - Fork 25k
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.
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
Clarify unassigned.reason
docs
#81017
Clarify unassigned.reason
docs
#81017
Conversation
Today we indicate that the `unassigned.reason` field in various APIs indicates the reason why a shard is unassigned. This isn't really true, it tells you some information about the event that caused the shard to _become_ unassigned (or which most recently changed its routing table entry while remaining unassigned) but tells you almost nothing about why the shard _is now_ unassigned and how to fix it. That's what the allocation explain API is for. This commit clarifies this point in the docs. Closes elastic#80892
Pinging @elastic/es-distributed (Team:Distributed) |
Pinging @elastic/es-docs (Team:Docs) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I left a few nits that you can take or leave. Thanks for fixing this.
Co-authored-by: James Rodewig <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this. I believe we should additionally call out cat shard's unassigned shards can help determine root cause of issue to avoid in the future
I'm not sure how to turn that into a concrete edit @stefnestor, would you suggest something more specific? In |
Today we indicate that the `unassigned.reason` field in various APIs indicates the reason why a shard is unassigned. This isn't really true, it tells you some information about the event that caused the shard to _become_ unassigned (or which most recently changed its routing table entry while remaining unassigned) but tells you almost nothing about why the shard _is now_ unassigned and how to fix it. That's what the allocation explain API is for. This commit clarifies this point in the docs. Closes elastic#80892 Co-authored-by: James Rodewig <[email protected]>
Today we indicate that the `unassigned.reason` field in various APIs indicates the reason why a shard is unassigned. This isn't really true, it tells you some information about the event that caused the shard to _become_ unassigned (or which most recently changed its routing table entry while remaining unassigned) but tells you almost nothing about why the shard _is now_ unassigned and how to fix it. That's what the allocation explain API is for. This commit clarifies this point in the docs. Closes elastic#80892 Co-authored-by: James Rodewig <[email protected]>
Today we indicate that the `unassigned.reason` field in various APIs indicates the reason why a shard is unassigned. This isn't really true, it tells you some information about the event that caused the shard to _become_ unassigned (or which most recently changed its routing table entry while remaining unassigned) but tells you almost nothing about why the shard _is now_ unassigned and how to fix it. That's what the allocation explain API is for. This commit clarifies this point in the docs. Closes #80892 Co-authored-by: James Rodewig <[email protected]> Co-authored-by: James Rodewig <[email protected]>
Today we indicate that the `unassigned.reason` field in various APIs indicates the reason why a shard is unassigned. This isn't really true, it tells you some information about the event that caused the shard to _become_ unassigned (or which most recently changed its routing table entry while remaining unassigned) but tells you almost nothing about why the shard _is now_ unassigned and how to fix it. That's what the allocation explain API is for. This commit clarifies this point in the docs. Closes #80892 Co-authored-by: James Rodewig <[email protected]> Co-authored-by: James Rodewig <[email protected]>
* upstream/master: (150 commits) Fix ComposableIndexTemplate equals when composed_of is null (elastic#80864) Optimize DLS bitset building for matchAll query (elastic#81030) URL option for BaseRunAsSuperuserCommand (elastic#81025) Less Verbose Serialization of Snapshot Failure in SLM Metadata (elastic#80942) Fix shadowed vars pt7 (elastic#80996) Fail shards early when we can detect a type missmatch (elastic#79869) Delegate Ref Counting to ByteBuf in Netty Transport (elastic#81096) Clarify `unassigned.reason` docs (elastic#81017) Strip blocks from settings for reindex targets (elastic#80887) Split off the values supplier for ScriptDocValues (elastic#80635) [ML] Switch message and detail for model snapshot deprecations (elastic#81108) [DOCS] Update xrefs for snapshot restore docs (elastic#81023) [ML] Updates visiblity of validate API (elastic#81061) Track histogram of transport handling times (elastic#80581) [ML] Fix datafeed preview with remote indices (elastic#81099) [ML] Fix acceptable model snapshot versions in ML deprecation checker (elastic#81060) [ML] Add logging for failing PyTorch test (elastic#81044) Extending the timeout waiting for snapshot to be ready (elastic#81018) [ML] Fix incorrect logging of unexpected model size error (elastic#81089) [ML] Make inference timeout test more reliable (elastic#81094) ... # Conflicts: # server/src/main/java/org/elasticsearch/index/mapper/NumberFieldMapper.java
* upstream/master: (55 commits) Fix ComposableIndexTemplate equals when composed_of is null (elastic#80864) Optimize DLS bitset building for matchAll query (elastic#81030) URL option for BaseRunAsSuperuserCommand (elastic#81025) Less Verbose Serialization of Snapshot Failure in SLM Metadata (elastic#80942) Fix shadowed vars pt7 (elastic#80996) Fail shards early when we can detect a type missmatch (elastic#79869) Delegate Ref Counting to ByteBuf in Netty Transport (elastic#81096) Clarify `unassigned.reason` docs (elastic#81017) Strip blocks from settings for reindex targets (elastic#80887) Split off the values supplier for ScriptDocValues (elastic#80635) [ML] Switch message and detail for model snapshot deprecations (elastic#81108) [DOCS] Update xrefs for snapshot restore docs (elastic#81023) [ML] Updates visiblity of validate API (elastic#81061) Track histogram of transport handling times (elastic#80581) [ML] Fix datafeed preview with remote indices (elastic#81099) [ML] Fix acceptable model snapshot versions in ML deprecation checker (elastic#81060) [ML] Add logging for failing PyTorch test (elastic#81044) Extending the timeout waiting for snapshot to be ready (elastic#81018) [ML] Fix incorrect logging of unexpected model size error (elastic#81089) [ML] Make inference timeout test more reliable (elastic#81094) ...
* upstream/master: (55 commits) Fix ComposableIndexTemplate equals when composed_of is null (elastic#80864) Optimize DLS bitset building for matchAll query (elastic#81030) URL option for BaseRunAsSuperuserCommand (elastic#81025) Less Verbose Serialization of Snapshot Failure in SLM Metadata (elastic#80942) Fix shadowed vars pt7 (elastic#80996) Fail shards early when we can detect a type missmatch (elastic#79869) Delegate Ref Counting to ByteBuf in Netty Transport (elastic#81096) Clarify `unassigned.reason` docs (elastic#81017) Strip blocks from settings for reindex targets (elastic#80887) Split off the values supplier for ScriptDocValues (elastic#80635) [ML] Switch message and detail for model snapshot deprecations (elastic#81108) [DOCS] Update xrefs for snapshot restore docs (elastic#81023) [ML] Updates visiblity of validate API (elastic#81061) Track histogram of transport handling times (elastic#80581) [ML] Fix datafeed preview with remote indices (elastic#81099) [ML] Fix acceptable model snapshot versions in ML deprecation checker (elastic#81060) [ML] Add logging for failing PyTorch test (elastic#81044) Extending the timeout waiting for snapshot to be ready (elastic#81018) [ML] Fix incorrect logging of unexpected model size error (elastic#81089) [ML] Make inference timeout test more reliable (elastic#81094) ...
Today we indicate that the
unassigned.reason
field in various APIsindicates the reason why a shard is unassigned. This isn't really true,
it tells you some information about the event that caused the shard to
become unassigned (or which most recently changed its routing table
entry while remaining unassigned) but tells you almost nothing about why
the shard is now unassigned and how to fix it. That's what the
allocation explain API is for. This commit clarifies this point in the
docs.
Closes #80892