Disk WatermarkThere are various watermark thresholds on an Elasticsearch cluster. As the disk fills up on a node, the 1st threshold to be crossed is...
Elasticsearch Cluster StateElasticsearch clusters need to maintain the cluster state in memory on each and every nodes, which requires a large amount of resources...
Elasticsearch Java Heap SizeHere's how to optimize the Elasticsearch Java Heap Size to ensure efficient resource utilization & prevent OutOfMemoryError issues.
Elasticsearch_disk_usage APIThe Elasticsearch _disk_usage API helps get information about disk usage for each analyzed field of indices and/or data streams. To use it...
Flood Stage Disk WatermarkWhen the “disk flood stage” threshold is exceeded on an Elasticsearch cluster, it will start to block core actions. To resolve this issue...
High Disk WatermarkHigh disk watermark is one of the various thresholds on your Elasticsearch cluster. Passing this threshold is a warning and you should not...
Loaded Data NodesSometimes 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 WatermarkLow disk watermark is one of the various thresholds on your Elasticsearch cluster. Here are possible actions you can take to resolve...
Memory Usage GuideThe Elasticsearch process is very memory intensive. Here are the memory requirements and some tips to reduce your Elasticsearch memory usage.
OvershardingA large number of shards on an Elasticsearch cluster requires extra resources. Learn key ways to avoid and correct oversharding...
Shard Allocation is UnbalancedShard allocation is an algorithm by which Elasticsearch decides which unallocated shards should go on which nodes. To resolve unbalanced...
Shards Too Large - Shard SizesIt is a best practice that Elasticsearch shard size should not go above 50GB for a single shard. If you go above this limit...