Allow allocating clones over low watermark #137399
Merged
Conversation
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
A new shard which is the result of a clone operation starts out on the same node as the shard being cloned and takes no additional space due to hard-linking, so we can safely allocate it even if the node is over the low watermark, and skip the checks that consider the additional space taken by the shard. Closes ES-13384
DaveCTurner added >bug :Distributed Coordination/Allocation 
Collaborator
| Hi @DaveCTurner, I've created a changelog YAML for you. |
elasticsearchmachine added Team:Distributed Coordination Collaborator
| Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
DaveCTurner added the auto-backport DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Oct 31, 2025
A new shard which is the result of a clone operation starts out on the same node as the shard being cloned and takes no additional space due to hard-linking, so we can safely allocate it even if the node is over the low watermark, and skip the checks that consider the additional space taken by the shard. Closes ES-13384
Collaborator
💚 Backport successful
|
elasticsearchmachine pushed a commit that referenced this pull request Oct 31, 2025
A new shard which is the result of a clone operation starts out on the same node as the shard being cloned and takes no additional space due to hard-linking, so we can safely allocate it even if the node is over the low watermark, and skip the checks that consider the additional space taken by the shard. Closes ES-13384
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.
A new shard which is the result of a clone operation starts out on the
same node as the shard being cloned and takes no additional space due to
hard-linking, so we can safely allocate it even if the node is over the
low watermark, and skip the checks that consider the additional space
taken by the shard.
Closes ES-13384