Unassigned shards on the node

Elastic Stack Elasticsearch
1

Cluster state is changed to red since there are 2 unassigned shards.

curl -s 'localhost:9200/_cat/shards' | fgrep UNASSIGNED
.kibana_task_manager_1                                              0 p UNASSIGNED                                 
.kibana_task_manager_1                                              0 r UNASSIGNED

curl -XGET localhost:9200/_cluster/allocation/explain?pretty gives the following results

"node_decision" : "no",
      "store" : {
        "in_sync" : true,
        "allocation_id" : "allocation_id",
        "store_exception" : {
          "type" : "shard_lock_obtain_failed_exception",
          "reason" : "[.kibana_task_manager_1][0]: obtaining shard lock timed out after 5000ms, previous lock details: [shard creation] trying to lock for [open index]",
          "index_uuid" : "index-uuid",
          "shard" : "0",
          "index" : ".kibana_task_manager_1"
        }
      },
      "deciders" : [
        {
          "decider" : "max_retry",
          "decision" : "NO",
          "explanation" : "shard has exceeded the maximum number of retries [5] on failed allocation attempts - manually call [/_cluster/reroute?retry_failed=true] to retry, [unassigned_info[[reason=ALLOCATION_FAILED], at[2021-02-03T02:49:56.691Z], failed_attempts[5], failed_nodes, delayed=false, details[failed shard on node [node-id]: failed to create shard, failure IOException[failed to obtain in-memory shard lock]; nested: ShardLockObtainFailedException[[.kibana_task_manager_1][0]: obtaining shard lock timed out after 5000ms, previous lock details: [shard creation] trying to lock for [shard creation]]; ], allocation_status[deciders_no]]]"
2

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