One index shows red status

Elastic Stack Elasticsearch
1

health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
red open hft-filebeat 2aHzkG-YRLODjaTR0IAErQ 1 0

Not sure why this shows red although have restarted services multiple times.

2

Welcome to our community! :smiley:

Check your Elasticsearch logs, it should mention what the issue is.

1 Like
3

when i fetch this index by GET /hft_filebeat ,it prints -

{
"error" : {
"root_cause" : [
{
"type" : "index_not_found_exception",
"reason" : "no such index [hft_filebeat]",
"resource.type" : "index_or_alias",
"resource.id" : "hft_filebeat",
"index_uuid" : "na",
"index" : "hft_filebeat"
}
],
"type" : "index_not_found_exception",
"reason" : "no such index [hft_filebeat]",
"resource.type" : "index_or_alias",
"resource.id" : "hft_filebeat",
"index_uuid" : "na",
"index" : "hft_filebeat"
},
"status" : 404
}

while all other 240 indexes are in green state.only this causing error..

also if i read logstasg service logs -- i get this -

retrying failed action with response code: 503 ({"type"=>"unavailable_shards_exception", "reason"=>"[hft-filebeat][0] primary shard is not active

4

Please check your Elasticsearch logs.

5

elasticsearch logs dont give much info but meanwhile i deleted red index and recreated it and elasticearch got green now..
can u tell me about docs.delete ?
do elasticsearch can ever delete files/folder of system as this single node is very crucial from data perspective as i often read elsaticseach file corrupt or deleted ?

6

hi , i am unable to see any data on kibana metric section..it shows no data to display...metricbeat logs says that cannot connect to 9200:elasticsearch..what could be possible reason ?

7

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.