Index is still red after recovery in Elasticsearch. How to turn it green? -
i working es 2.2
after index recovery with
post /_snapshot/s3_repository/snapshot_traces_291215/_restore { "include_global_state": false }
my index still red red open traces_v2 3 1
here cluster health:
{ "cluster_name": "burst", "status": "red", "timed_out": false, "number_of_nodes": 1, "number_of_data_nodes": 1, "active_primary_shards": 0, "active_shards": 0, "relocating_shards": 0, "initializing_shards": 0, "unassigned_shards": 6, "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": 0 }
i sure recovery complete. checked get /_cat/recovery?v
get /_cat/_shards?v
gives me:
index shard prirep state docs store ip node traces_v2 2 p unassigned traces_v2 2 r unassigned traces_v2 1 p unassigned traces_v2 1 r unassigned traces_v2 0 p unassigned traces_v2 0 r unassigned
could there version incompatibility between snapshot of 2.1 , es 2.2?
i forced assignation of primaries shards node by.
get _cluster/reroute { "commands" : [ { "allocate" : { "index" : "traces_v2", "shard" : "2", "node" : "killer shrike", "allow_primary" : true } } ] }
but status still yellow because run es on single node , had 3 replica shards. , replica shards can't run on node has primary shard.
so deleted them setting number of replica shards index 0.
put /_settings { "index" : { "number_of_replicas" : 0 } }
i hope other noob people me!
Comments
Post a Comment