Elasticsearch(25)
-
Elasticsearch rejected: {"error":{"root_cause":[{"type":"invalid_index_name_exception","reason":"Invalid index name [HOME], must be lowercase","index_uuid":"_na_","index":"HOME"}],"type":"invalid_index_name_exception","reason":"Invalid index name [HOME],
elasticsearch의 index이름은 대문자 사용안됨
2025.03.22 -
elasticsearch version 확인
GET /
2025.03.16 -
status가 'red'일 때 조치
# cluster 상태 확인curl -XGET "http://localhost:9200/_cluster/health?pretty"# red 상태인 indices 확인curl -XGET "http://localhost:9200/_cat/indices?health=red&v"# yellow 상태인 indices 확인curl -XGET "http://localhost:9200/_cat/indices?health=yellow&v"# UNASSIGNED 상태인 indices 확인curl -XGET "http://localhost:9200/_cat/shards?v" | grep UNASSIGNED# UNASSIGNED 원인 확인curl -XGET "http://localhost:9200/_cluster/alloca..
2025.03.03 -
elasticsearch self monitoring 여부 확인
셋팅 확인enabled:true이면 자체 모니터링 사용중curl -X GET "http://localhost:9200/_cluster/settings?include_defaults=true&pretty"# 결과 "xpack": { "monitoring": { "collection": { "enabled": "true" } }indices 확인.monitoring-*에 해당하는 indices가 있으면 자체 모니터링 사용중curl -X GET "http://localhost:9200/_cat/indices/.monitoring-*?v"# 결과green open .monitoring-es-7-2025.03.01 ...metricbeat 작동 ..
2025.03.02 -
max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]; for more information
원인: node의 max_map_count 용량이 작아서 발생한 문제조치방법1: node에 직접 설정# 임시sudo sysctl -w vm.max_map_count=262144# 영구echo "vm.max_map_count=262144" | sudo tee -a /etc/sysctl.confsudo sysctl -p방법2: daemonset 추가apiVersion: apps/v1kind: DaemonSetmetadata: name: sysctl-settings namespace: kube-systemspec: selector: matchLabels: name: sysctl-settings template: metadata: labels: name: sysc..
2025.03.01 -
Elasticsearch max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
This setting controls the number of memory-mapped areas for a process.Elasticsearch requires at least 262144 for performance.If it is too low, Elasticsearch cannot allocate enough memory pages, causing crashes.조치initContainers:- name: fix-permissions image: busybox command: ["sh", "-c", "sysctl -w vm.max_map_count=262144"] securityContext: privileged: true # 확인kubectl logs -f {pod} -n {..
2025.02.15