(Doc+) Split API | add where need to have sufficient disk and how much #119784
Conversation
This file contains 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
👋 howdy, ES Dev! Will you kindly confirm for [Split API](https://www.elastic.co/guide/en/elasticsearch/reference/master/indices-split-index.html) doc 1. Current doc states ... . My belief is that we're telling customers they need sufficient disk on each node hosting primary shards of the index which are going to be split out. AFAICT the doc does not currently otherwise help users judge which node will "handle the split process" which could randomly be master-only in which case this callout would feel wrong. > The node handling the split process must have sufficient free disk space to accommodate a second copy of the existing index. 2. If Elastic Cloud [hard-link not supported](https://support.elastic.dev/knowledge/view/d2cd7697) (internal link) restriction is ongoing? 🙏 TIA!
stefnestor
added
>docs
|
Documentation preview: |
|
@stefnestor please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-data-management (Team:Data Management) |
elasticsearchmachine
added
v9.0.0
external-contributor
|
Hi! This is a drive-by comment that the page affected by this PR will be removed from the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
👋 howdy, ES Dev!
Will you kindly confirm for Split API doc
Current doc states ... . My belief is that we're telling customers they need sufficient disk on each node hosting primary shards of the index which are going to be split out. AFAICT the doc does not currently otherwise help users judge which node will "handle the split process" which could randomly be master-only in which case this callout would feel invalid.
If Elastic Cloud hard-link not supported (internal link) restriction is ongoing?
TLDR: Can we add expectations about where split api's created primary shards will allocate so users know where to ensure sufficient disk?
🙏 TIA!