Skip to content

Conversation

@DaveCTurner
Copy link
Contributor

Backports the following commits to 9.2:

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 DaveCTurner added :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >bug auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Distributed Coordination Meta label for Distributed Coordination team labels Oct 31, 2025
@elasticsearchmachine elasticsearchmachine merged commit 69e2512 into elastic:9.2 Oct 31, 2025
34 checks passed
@DaveCTurner DaveCTurner deleted the backport/9.2/pr-137399 branch October 31, 2025 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >bug :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) Team:Distributed Coordination Meta label for Distributed Coordination team v9.2.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants