I am preparing to upgrade from elastic 5.6 to 6.6 and before production I did the test upgrade on small 3 cluster environemnt with 48 shards with no replicas. The upgrade seems to went well, no errors.
But the status of cluster is just RED and all shards are UNASSIGNED
# curl 'http://elast:9200/_cluster/health?pretty' {
"cluster_name" : "graylog-st",
"status" : "red",
"timed_out" : false,
"number_of_nodes" : 3,
"number_of_data_nodes" : 3,
"active_primary_shards" : 0,
"active_shards" : 0,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 48,
"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.0
}
and whem looking into shards why they dont start it returns for every shard the same info:
"cluster_name" : "graylog-st",
"compressed_size_in_bytes" : 30633,
"cluster_uuid" : "bcUJt_Q",
"routing_table" : {
"indices" : {
"graylog_5135" : {
"shards" : {
"1" : [
{
"state" : "UNASSIGNED",
"primary" : true,
"node" : null,
"relocating_node" : null,
"shard" : 1,
"index" : "graylog_5135",
"recovery_source" : {
"type" : "EXISTING_STORE",
"bootstrap_new_history_uuid" : false
},
"unassigned_info" : {
"reason" : "CLUSTER_RECOVERED",
"at" : "2019-04-08T12:05:15.462Z",
"delayed" : false,
"allocation_status" : "no_valid_shard_copy"
}
},
{
"state" : "UNASSIGNED",
"primary" : false,
"node" : null,
"relocating_node" : null,
"shard" : 1,
"index" : "graylog_5135",
"recovery_source" : {
"type" : "PEER"
},
"unassigned_info" : {
"reason" : "CLUSTER_RECOVERED",
"at" : "2019-04-08T12:05:15.462Z",
"delayed" : false,
"allocation_status" : "no_attempt"
}
}
],