Elasticsearch: Difference between revisions

From DWIKI
Line 13: Line 13:
*[https://sematext.com/blog/java-garbage-collection/#how-does-java-garbage-collection-work Garbage collection]
*[https://sematext.com/blog/java-garbage-collection/#how-does-java-garbage-collection-work Garbage collection]
*[https://opster.com/guides/elasticsearch/capacity-planning/elasticsearch-heap-size-usage/ Elasticsearch Heap Size Usage and JVM Garbage Collection]
*[https://opster.com/guides/elasticsearch/capacity-planning/elasticsearch-heap-size-usage/ Elasticsearch Heap Size Usage and JVM Garbage Collection]
Ideally:
*Young GC is processed quickly (within 50 ms).
*Young GC is not frequently executed (about 10 seconds).
*Old GC is processed quickly (within 1 second).
*Old GC is not frequently executed (once per 10 minutes or more).


=Monitoring elasticsearch=
=Monitoring elasticsearch=

Revision as of 14:27, 28 August 2023

Links

Documentation

Configuration

Heap

Garbage collection

Ideally:

  • Young GC is processed quickly (within 50 ms).
  • Young GC is not frequently executed (about 10 seconds).
  • Old GC is processed quickly (within 1 second).
  • Old GC is not frequently executed (once per 10 minutes or more).

Monitoring elasticsearch

Things to monitor

heap size

  • node jvm.mem.heap_used_percent

garbage collection

Something like

node.jvm.uptime_in_millis/node.jvm.gc.collectors.young.collection_count

Query the web interface

Installing Elasticsearch

On Debian

deb https://artifacts.elastic.co/packages/oss-6.x/apt stable main

packages is called elasticsearch-oss now?

Terminology

shards

"blocks" of index data distributed over the nodes

Percolation

https://spinscale.de/posts/2021-09-15-understanding-elasticsearch-percolate-query.html

FAQ

Status is yellow

and look for unassigned shards