Elasticsearch Enable Adaptive Replica Selection



Elasticsearch Enable Adaptive Replica Selection

Opster Team

July 2020, Version: 1.7-7.9


In addition to reading this guide, run the free Elasticsearch Health Check-Up. Get actionable recommendations that can improve performance and prevent incidents (does not require any installation). Among the dozens of checks included are: shards sizes, search errors, thread pools, management queue size, circuit breakers and many more. Join over 700 users who use this free tool.

What Does it Mean?

Adaptive replica selection is a process intended to prevent a distressed Elasticsearch node from delaying the response to queries, while reducing the search load on that node.

To understand how it works, imagine a situation where a single node is in distress. This could be because of hardware, network or configuration issues, but as a consequence the response time for shards on that node are much longer than the response time from the other nodes.

When an Elasticsearch node receives a query, it needs to receive a response from all of the shards in all of the indices covered by that query so multiple nodes are usually involved in producing the response. Without adaptive replica selection, Elasticsearch would check which replicas are available from all the nodes including the node in distress, and request responses for each shard from the other nodes based on a “round robin” approach. Using adaptive replica selection, Elasticsearch will only request data from shards on a distressed node when there is no other alternative (i.e. when there are no other replicas), resulting in reduced load on distressed nodes, and shorter response times.

How to Resolve 

By default, adaptive replica selection is enabled in version 7 and onwards. You can enable it in version 6.1 onwards by running the following:

PUT /_cluster/settings
{
  "transient": {
    "cluster.routing.use_adaptive_replica_selection": true
  }
}




Improve Elasticsearch Performance

Run The Analysis