Elasticsearch on AWS RED and redirection not allowed

I created an ES domain to search for vpcglow logs and a daily indexed cloud trail log. Now RED status:

{ "cluster_name": "678628912247:test", "status": "red", "timed_out": false, "number_of_nodes": 17, "number_of_data_nodes": 17, "active_primary_shards": 687, "active_shards": 1374, "relocating_shards": 0, "initializing_shards": 0, "unassigned_shards": 8, "number_of_pending_tasks": 0 } 

Further research, I found one index RED:

 red open cwl-2016.02.19 5 1 381700 102899 335.8mb 167.9mb 

Looking at the fragments:

 cwl-2016.02.19 2 p UNASSIGNED cwl-2016.02.19 2 r UNASSIGNED cwl-2016.02.19 0 p UNASSIGNED cwl-2016.02.19 0 r UNASSIGNED cwl-2016.02.19 3 p STARTED 381700 167.9mb xxxx Elektra Natchios cwl-2016.02.19 3 r STARTED 381700 167.9mb xxxx Chronos cwl-2016.02.19 1 p UNASSIGNED cwl-2016.02.19 1 r UNASSIGNED cwl-2016.02.19 4 p UNASSIGNED cwl-2016.02.19 4 r UNASSIGNED 

I tried redirecting the fragments to less used nodes, but it gives me:

 {"Message":"Your request: '/_cluster/reroute' is not allowed."} 

Any advice, please, what should I do now.

Thanks and respect.

+6
source share
1 answer

A red cluster status means that at least one primary segment and its replicas are not allocated to a node.

Since you have already found the red index, it is best to remove it. If deletion is not possible, you will restore the snapshot (note that AWS automatically takes snapshots)

As a last resort, you can contact AWS Support and they can restore it for you.

It is important to fix the red cluster, because when the cluster turns red, AWS stops taking automatic snapshots.

0
source

All Articles