Hi everyone,
I have a question about how load balance work on an elasticsearch servers cluster.
The cluster is composed by :
- 4 "master, data" nodes,
- 2 "data" nodes
- 1 "coordinator" node
The warning "high disk watermark [90%] exceeded" is displayed in the logstash log file, and documents are no longer saved in the elasticsearch index.
After checking all the elasticsearch nodes in the cluster, it appears that for 2 nodes, disks are used over 90%.
So my question are :
- why elasticsearch does not send documents to the available nodes ? or is it a normal behavior to be bloked if a node is down (i don't think so...) ?
- I'm not an expert but it seems like a sharding problem due to the cluster's settings. May be i missed a configuration. Right ?
- what are the steps to "re up" my cluster and documents saving
In the logstash configuration file, output to elastic is set as :
output { elasticsearch { hosts => ["host_1:port", "host_2:port", "host_3:port",...."host_n:port"] } ...}
and communication between Logstash and the elasticsearch cluster is through SSL protocol.
For information, here is the reuslt of GET /_cat/indices/?v=true
:
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open idx-aggregated-logs-000001 qJJE4BUTQYyj9ExIUegJBQ 1 1 511638025 0 747.4gb 373.7gb
And the result of GET /_cat/shards
.ds-ilm-history-5-2022.08.31-000004 0 p STARTED 100.132.166.8 bil192939.prv.cloud
.ds-ilm-history-5-2022.08.31-000004 0 r STARTED 100.132.166.6 bil198688.prv.cloud
idx-aggregated-logs-000001 0 r STARTED 511638025 373.6gb 100.132.99.14 bil192488.prv.cloud
idx-aggregated-logs-000001 0 p STARTED 511638025 373.7gb 100.132.99.13 bil196016.prv.cloud
.ds-.logs-deprecation.elasticsearch-default-2022.08.10-000001 0 p STARTED 100.132.99.12 bil196860.prv.cloud
.ds-.logs-deprecation.elasticsearch-default-2022.08.10-000001 0 r STARTED 100.132.166.14 bil196062.prv.cloud
.ds-.logs-deprecation.elasticsearch-default-2022.08.24-000002 0 p STARTED 100.132.99.10 bil195277.prv.cloud
.ds-.logs-deprecation.elasticsearch-default-2022.08.24-000002 0 r STARTED 100.132.99.8 bil197728.prv.cloud
.ds-ilm-history-5-2022.06.02-000001 0 p STARTED 100.132.166.13 bil190257.prv.cloud
.ds-ilm-history-5-2022.06.02-000001 0 r STARTED 100.132.99.7 bil193961.prv.cloud
.ds-ilm-history-5-2022.08.01-000003 0 p STARTED 100.132.166.6 bil198688.prv.cloud
.ds-ilm-history-5-2022.08.01-000003 0 r STARTED 100.132.166.7 bil197047.prv.cloud
.ds-ilm-history-5-2022.07.02-000002 0 p STARTED 100.132.166.8 bil192939.prv.cloud
.ds-ilm-history-5-2022.07.02-000002 0 r STARTED 100.132.166.7 bil197047.prv.cloud
Thx for your help,
Khaled