Avoid async cache-size fetch on partial shards #68644
Merged
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
Today we perform an async fetch for every searchable snapshot shard while allocating it, so that we can prefer to allocate it to the node that holds the warmest cache for that shard. For partial shards, there is no persistently-cached data to reuse, so we can skip the async fetch.
DaveCTurner
added
>enhancement
:Distributed/Snapshot/Restore
|
Pinging @elastic/es-distributed (Team:Distributed) |
|
Thanks @tlrx |
DaveCTurner
added a commit
that referenced
this pull request
Feb 8, 2021
Today we perform an async fetch for every searchable snapshot shard while allocating it, so that we can prefer to allocate it to the node that holds the warmest cache for that shard. For partial shards, there is no persistently-cached data to reuse, so we can skip the async fetch.
easyice
pushed a commit
to easyice/elasticsearch
that referenced
this pull request
Mar 25, 2021
Today we perform an async fetch for every searchable snapshot shard while allocating it, so that we can prefer to allocate it to the node that holds the warmest cache for that shard. For partial shards, there is no persistently-cached data to reuse, so we can skip the async fetch.
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.
Today we perform an async fetch for every searchable snapshot shard
while allocating it, so that we can prefer to allocate it to the node
that holds the warmest cache for that shard. For partial shards, there
is no persistently-cached data to reuse, so we can skip the async fetch.