Elasticsearch settings
Warning
Yandex Managed Service for Elasticsearch is unavailable as of April 11, 2024.
You can create an OpenSearch cluster in Yandex Cloud as an alternative to Elasticsearch.
For Managed Service for Elasticsearch clusters, you can configure Elasticsearch settings.
The label next to the setting name shows which interface can be used to configure this setting: the management console, CLI, API, or Terraform. The All interfaces
label means that all of the above interfaces are supported.
Depending on the selected interface, the same setting may be represented in a different way, e.g.:
-
Fielddata cache size in the management console is:
fielddata_cache_size
in the gRPC API, CLI, and Terraform.fielddataCacheSize
in the REST API.
Cluster-level settings
You can use the following settings:
-
Fielddata cache size
All interfaces
Maximum cache size allocated to field data. Specified as a string containing a relative (
20%
) or absolute (12GB
) value. The maximum value is equal to40%
of the JVM heap. There is no default value, as the amount of cache allocated to field data is not limited.For more information, see the Elasticsearch documentation
. -
Reindex remote whitelist
API
This is a comma-separated list of host IP addresses or FQDNs, as well as host ports that may be used as a remote source for the Reindex API
.You can use the
*
wildcard character to specify an IP or port range, such as:hostname:9200, 192.168.0.*:9200, localhost:*
For more information, see the Elasticsearch documentation
. -
Reindex SSL CA path
API
The local path to the certificate file for the cluster to use to encrypt the connection to the remote source for the Reindex API
.Add the certificate file as an extension to the cluster and specify the path as:
/etc/elasticsearch/extensions/<extension_name>/<certificate_name>
For more information, see the Elasticsearch documentation
.