Difference between revisions of "Elasticsearch troubleshooting"
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
[[systemctl restart]] [[elasticsearch]] && [[systemctl status elasticsearch]] && tail -f [[/var/log/elasticsearch/elasticsearch.log]] | [[systemctl restart]] [[elasticsearch]] && [[systemctl status elasticsearch]] && tail -f [[/var/log/elasticsearch/elasticsearch.log]] | ||
[[Elasticsearch logs]] | [[Elasticsearch logs]] | ||
| + | [[gateway.auto_import_dangling_indices]] | ||
== See also == | == See also == | ||
Revision as of 17:12, 12 December 2023
curl http://localhost:9200/_cluster/health?pretty -k -u'admin:adminpass'curl -k "https://localhost:9200/_cat/indices?v&health=yellow" -u'XXX:UUU'curl -k "https://localhost:9200/_cat/indices?v&health=red" -u'XXX:UUU'
Elasticsearch storage
Messages
Java.io.IOException: failed to obtain in-memory shard lockLow disk watermarkhigh disk watermarkCluster health status changed from [YELLOW] to [GREEN]No search context found for idNo space left on device
Related
/_cluster/settings GET /_cluster/allocation/explain green, yellow, red WARN, INFO, DEBUG elasticsearch.yml uuid systemctl restart elasticsearch && systemctl status elasticsearch && tail -f /var/log/elasticsearch/elasticsearch.log Elasticsearch logs gateway.auto_import_dangling_indices
See also
Advertising:
