In addition to reading this guide, we recommend you run the Elasticsearch Health Check-Up. It will detect issues and improve your Elasticsearch performance by analyzing your shard sizes, threadpools, memory, snapshots, disk watermarks and more.The Elasticsearch Check-Up is free and requires no installation.
Before you begin reading this guide, we recommend you try running the OpenSearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.
To easily resolve issues in your deployment and locate their root cause, try AutoOps for OpenSearch. AutoOps will also help you optimize other important settings in OpenSearch to improve performance.
Overview
In OpenSearch, persistent refers to cluster settings that persist across cluster restarts. This setting is used in Cluster Update API calls. Persistent settings can also be configured in the opensearch.yml file.
Examples
## enable shard routing PUT /_cluster/settings { "persistent" : { "cluster.routing.allocation.enable" : "all" } } ## enable rebalancing of shards PUT /_cluster/settings { "persistent" : { "cluster.routing.rebalance.enable" : "all" } } ## limit the heap size for fielddata PUT /_cluster/settings { "persistent" : { “indices.breaker.fielddata.limit”: "30%" } }