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.

Sign up for GitHub

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

[Backport 2.18] Removing outdated limitations in Searchable Snapshots describing KNN is not compatible. #8877

Merged
merged 1 commit into from
Dec 4, 2024
Merged

[Backport 2.18] Removing outdated limitations in Searchable Snapshots describing KNN is not compatible. #8877

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions _tuning-your-cluster/availability-and-recovery/snapshots/searchable_snapshot.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ services:
- node.search.cache.size=50gb
```


- Starting with version 2.18, k-NN indexes support searchable snapshots for the NMSLIB and Faiss engines.

## Create a searchable snapshot index

Expand Down Expand Up @@ -109,4 +109,3 @@ The following are known limitations of the searchable snapshots feature:
- Searching remote data can impact the performance of other queries running on the same node. We recommend that users provision dedicated nodes with the `search` role for performance-critical applications.
- For better search performance, consider [force merging]({{site.url}}{{site.baseurl}}/api-reference/index-apis/force-merge/) indexes into a smaller number of segments before taking a snapshot. For the best performance, at the cost of using compute resources prior to snapshotting, force merge your index into one segment.
- We recommend configuring a maximum ratio of remote data to local disk cache size using the `cluster.filecache.remote_data_ratio` setting. A ratio of 5 is a good starting point for most workloads to ensure good query performance. If the ratio is too large, then there may not be sufficient disk space to handle the search workload. For more details on the maximum ratio of remote data, see issue [#11676](https://github.com/opensearch-project/OpenSearch/issues/11676).
- k-NN native-engine-based indexes using `faiss` and `nmslib` engines are incompatible with searchable snapshots.
Loading