{"@timestamp":"2023-04-24T08:01:14.916Z", "log.level": "INFO", "message":"started restore of snapshot [test:daily-snap-2023.04.24-11fpwyahtqelkiworchbnq/cdWViVs-QT-Gdp3XRZMu2A] for indices [.kibana_task_manager_8.6.2_001, .apm-custom-link, .apm-agent-configuration, .kibana-event-log-8.6.2-000001, test-2023-04-24-07-55, .kibana_8.6.2_001, test-2023-04-24-07-54, .ds-ilm-history-5-2023.04.24-000001]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch][masterService#updateTask][T#1]","log.logger":"org.elasticsearch.snapshots.RestoreService","trace.id":"e45e03ff0561926327a206e8e813b002","elasticsearch.cluster.uuid":"z3W3chrVS0iPwx_kDSzOWg","elasticsearch.node.id":"A2ir0esJSuibDLJDU35kGg","elasticsearch.node.name":"elasticsearch","elasticsearch.cluster.name":"docker-cluster"}
{"@timestamp":"2023-04-24T08:01:14.941Z", "log.level": "INFO", "current.health":"RED","message":"Cluster health status changed from [YELLOW] to [RED] (reason: [reconcile-desired-balance]).","previous.health":"YELLOW","reason":"reconcile-desired-balance" , "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch][masterService#updateTask][T#1]","log.logger":"org.elasticsearch.cluster.routing.allocation.AllocationService","trace.id":"e45e03ff0561926327a206e8e813b002","elasticsearch.cluster.uuid":"z3W3chrVS0iPwx_kDSzOWg","elasticsearch.node.id":"A2ir0esJSuibDLJDU35kGg","elasticsearch.node.name":"elasticsearch","elasticsearch.cluster.name":"docker-cluster"}
{"@timestamp":"2023-04-24T08:01:14.994Z", "log.level": "INFO", "message":"completed restore of snapshot [test:daily-snap-2023.04.24-11fpwyahtqelkiworchbnq/cdWViVs-QT-Gdp3XRZMu2A]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch][masterService#updateTask][T#1]","log.logger":"org.elasticsearch.snapshots.RestoreService","trace.id":"e45e03ff0561926327a206e8e813b002","elasticsearch.cluster.uuid":"z3W3chrVS0iPwx_kDSzOWg","elasticsearch.node.id":"A2ir0esJSuibDLJDU35kGg","elasticsearch.node.name":"elasticsearch","elasticsearch.cluster.name":"docker-cluster"}
ELK 구축 중 Kibana 주소로 접속을 해 보면
kibana server is not ready yet 메세지가 발생하고
elasticsearch의 로그를 확인해보니
위와 같은 에러가 발생하고 있었는데 원인을 확인해보니
구축하는 드라이브에서 85% 이상의 용량을 사용하고 있을 경우
위와 같은 에러가 발생하게 되는데
용량을 늘려준 뒤 다시 ELK를 띄워보면
에러 없이 잘 동작한다
'Tools > Infra' 카테고리의 다른 글
AWS 탄력적 IP 주소 삭제방법 (0) | 2023.06.06 |
---|---|
elasticsearch exception during geoip 해결방법 (0) | 2023.04.26 |
댓글