Capacity planning

Choosing the right amount of memory based on number of shards in Elasticsearch

If the ratio of memory to number of shards in the cluster is low, it suggests that you have insufficient memory compared to the volume...

Disk Watermark

There are various watermark thresholds on an Elasticsearch cluster. As the disk fills up on a node, the 1st threshold to be crossed is...

Elastic Pricing Calculator - How to Use the Elastic Pricing Calculator

The different categories in the Elastic Pricing Calculator can impact your final cost. Here's how to efficiently use the pricing calculator.

Elasticsearch Cluster State

Elasticsearch clusters need to maintain the cluster state in memory on each and every nodes, which requires a large amount of resources...

Elasticsearch Large Cluster State - How to Discover, Resolve and Prevent (Customer Post Mortem)

When cluster state becomes too large it poses many challenges. In order to determine the size of your cluster state and reduce it, you...

Elasticsearch Multi-Tier Architecture - How to Set Up a Hot/Warm/Cold/Frozen Elasticsearch Architecture

In Elasticsearch’s multi-tier architecture, the tiers are named hot, warm, cold & frozen. This Elasticsearch architecture allows better...

Flood Stage Disk Watermark

When the “disk flood stage” threshold is exceeded on an Elasticsearch cluster, it will start to block core actions. To resolve this issue...

Heap Size Usage and JVM Garbage Collection

A high heap size in Elasticsearch will give your node more memory for indexing and search operations. However, your node also requires...

High Disk Watermark

High disk watermark is one of the various thresholds on your Elasticsearch cluster. Passing this threshold is a warning and you should not...

How to Choose the Correct Number of Shards per Index in Elasticsearch

Finding the right number of shards for your Elasticsearch indices, and the right size for each shard depends on many factors, including...

How to Optimize Elasticsearch Disk Space and Usage

If you don’t have enough disk space available, Elasticsearch will stop allocating shards to the node. This will eventually prevent you from...

How to Reduce the Number of Shards in an Elasticsearch Cluster

When you have too many shards in your Elasticsearch cluster, there are a few steps you can take in order to reduce the number of shards...

Loaded Data Nodes

Sometimes you can observe that the CPU and load on some of your data nodes is higher than on others. This can occasionally be caused by...

Low Disk Watermark

Low disk watermark is one of the various thresholds on your Elasticsearch cluster. Here are possible actions you can take to resolve...

Memory Usage Guide

The Elasticsearch process is very memory intensive. Here are the memory requirements and some tips to reduce your Elasticsearch memory usage.

Oversharding

A large number of shards on an Elasticsearch cluster requires extra resources. Learn key ways to avoid and correct oversharding...

Shard Allocation is Unbalanced

Shard allocation is an algorithm by which Elasticsearch decides which unallocated shards should go on which nodes. To resolve unbalanced...

Shards Too Large

It is a best practice that Elasticsearch shard size should not go above 50GB for a single shard. If you go above this limit...

Skip to content