How to recover unassigned shards and replica for a index

Elastic Stack Elasticsearch
1

HI team,
I want to know how to recover the red state into Green and when it try to find the reason and im getting below data,

xx-logstash-2020.07 0 p INITIALIZING INDEX_REOPENED
xx-logstash-2020.07 0 r UNASSIGNED INDEX_REOPENED
xx-logstash-2020.07 0 r UNASSIGNED INDEX_REOPENED

I dont want to loss any data on that index.

How to recover without losing any information.

2

As it is initializing I guess you will need to wait. How many indices and shards do you have in the cluster? How did the cluster end up in this state?

3

@Christian_Dahlqvist thanks for the reply, Due to disk 100% per Utilization it end up this state.

My cluster detail below,

{
"cluster_name": "xxxxx",
"status": "red",
"timed_out": false,
"number_of_nodes": 8,
"number_of_data_nodes": 3,
"active_primary_shards": 82,
"active_shards": 179,
"relocating_shards": 0,
"initializing_shards": 1,
"unassigned_shards": 2,
"delayed_unassigned_shards": 0,
"number_of_pending_tasks": 0,
"number_of_in_flight_fetch": 0,
"task_max_waiting_in_queue_millis": 0,
"active_shards_percent_as_number": 98.35164835164835
}

4

Reduce the number of replicas to 1 for any indices with a higher number configured in order to save space. Then delete data if needed.

5

will it help to reduce my replica for that index,

PUT xxlogstash-2020.07/_settings
{
"index" : {
"number_of_replicas" : 0
}
}

6

If you are lacking space I think you will need to do it for other indices that are already allocated in order to free up space.

7

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