Skip to content

Commit

Permalink
Disambiguate statement "value defaults to a fixed percentage"
Browse files Browse the repository at this point in the history
This page documents that "In the case of a dedicated search node where the node exclusively has the search role, this value defaults to a fixed percentage of available storage."

However, the document does not provide specifics about what this fixed percentage is. From what I can surmise reading the code, and from doing real world testing, this value is set to 80% of the available space on the volume where the file cache lives.

Signed-off-by: Drew Miranda <[email protected]>
  • Loading branch information
drewmiranda-gl committed Sep 24, 2024
1 parent 53b650f commit f8f7bd4
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ The searchable snapshot feature incorporates techniques like caching frequently

To configure the searchable snapshots feature, create a node in your `opensearch.yml file` and define the node role as `search`. Optionally, you can also configure the `cache.size` property for the node.

A `search` node reserves storage for the cache to perform searchable snapshot queries. In the case of a dedicated search node where the node exclusively has the `search` role, this value defaults to a fixed percentage of available storage. In other cases, the value needs to be configured by the user using the `node.search.cache.size` setting.
A `search` node reserves storage for the cache to perform searchable snapshot queries. In the case of a dedicated search node where the node exclusively has the `search` role, this value defaults to a fixed percentage (80%) of available storage. In other cases, the value needs to be configured by the user using the `node.search.cache.size` setting.

Parameter | Type | Description
:--- | :--- | :---
Expand Down

0 comments on commit f8f7bd4

Please sign in to comment.