Elasticsearch Persistent



Elasticsearch Persistent

Opster Team

July 2020, Version: 1.7-8.0


Before you begin reading the explanation below, try running the free ES Health Check-Up get actionable recommendations that can improve Elasticsearch performance and prevent serious incidents. Just 2 minutes to complete and you can check your threadpools, memory, snapshots and many more

Persistent in Elasticsearch

What it is

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 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 >


About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now