Skip to content
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

Make blob cache have async durability #66687

Conversation

henningandersen
Copy link
Contributor

The blob cache for searchable snapshots used default sync durability.
Indexing into this often comes in bursts (multiple files for a shard or
multiple shards for an index or even multiple indexes being mounted) and
since it is immutable and easily reconstructed, this commit changes
durability to async. This improves mount performance when blob cache
index is co-located with the searchable snapshot(s).

The blob cache for searchable snapshots used default sync durability.
Indexing into this often comes in bursts (multiple files for a shard or
multiple shards for an index or even multiple indexes being mounted) and
since it is immutable and easily reconstructed, this commit changes
durability to async. This improves mount performance when blob cache
index is co-located with the searchable snapshot(s).
@elasticmachine elasticmachine added the Team:Distributed Meta label for distributed team label Dec 21, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

Copy link
Member

@tlrx tlrx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@henningandersen
Copy link
Contributor Author

@elasticmachine update branch

@henningandersen henningandersen merged commit 3218745 into elastic:master Dec 29, 2020
henningandersen added a commit to henningandersen/elasticsearch that referenced this pull request Dec 29, 2020
The blob cache for searchable snapshots used default sync durability.
Indexing into this often comes in bursts (multiple files for a shard or
multiple shards for an index or even multiple indexes being mounted) and
since it is immutable and easily reconstructed, this commit changes
durability to async. This improves mount performance when blob cache
index is co-located with the searchable snapshot(s).
henningandersen added a commit that referenced this pull request Dec 29, 2020
The blob cache for searchable snapshots used default sync durability.
Indexing into this often comes in bursts (multiple files for a shard or
multiple shards for an index or even multiple indexes being mounted) and
since it is immutable and easily reconstructed, this commit changes
durability to async. This improves mount performance when blob cache
index is co-located with the searchable snapshot(s).
henningandersen added a commit that referenced this pull request Dec 29, 2020
The blob cache for searchable snapshots used default sync durability.
Indexing into this often comes in bursts (multiple files for a shard or
multiple shards for an index or even multiple indexes being mounted) and
since it is immutable and easily reconstructed, this commit changes
durability to async. This improves mount performance when blob cache
index is co-located with the searchable snapshot(s).
alyokaz pushed a commit to alyokaz/elasticsearch that referenced this pull request Mar 10, 2021
The blob cache for searchable snapshots used default sync durability.
Indexing into this often comes in bursts (multiple files for a shard or
multiple shards for an index or even multiple indexes being mounted) and
since it is immutable and easily reconstructed, this commit changes
durability to async. This improves mount performance when blob cache
index is co-located with the searchable snapshot(s).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >enhancement Team:Distributed Meta label for distributed team v7.11.1 v7.12.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants