Elasticsearch Persistent

Average Read Time

1 Mins

Elasticsearch Persistent

Opster Team

October 2021

Average Read Time

1 Mins


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.

Run the Elasticsearch check-up to receive recommendations like this:

checklist Run Check-Up
error

The following configuration error was detected on node 123...

error-img

Description

This error can have a severe impact on your system. It's important to understand that it was caused by...

error-img

Recommendation

In order to resolve this issue and prevent it from occurring again, we recommend that you begin by changing the configuration to...

1

X-PUT curl -H "Content-Type: application/json" [customized recommendation]

Overview

In Elasticsearch, 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 elasticsearch.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%"
    }
}

Related log errors to this ES concept


Task failed with an exception
Trying to update state on non-existing task
Failed to remove datafeed persistent task will not auto close job
Persistent task
Attempt to complete task with id in the state
Failed to reassign persistent tasks
Trying to update state on task with unexpected allocation id
Persistent task with id and allocation id failed to create
The task with id was found but it has a different allocation id ; status is not updated
The task wasnt found; status is not updated
Un-assigning persistent tasks :
Ignoring persistent setting ;

< Page: 1 of 2 >


Run the Check-Up to get a customized report like this:

Analyze your cluster