Advertisement
Zorobay

index status

Mar 13th, 2019
160
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
JSON 2.62 KB | None | 0 0
  1. {
  2.     "index": "cpi_sensors_shipped",
  3.     "shard": 0,
  4.     "primary": true,
  5.     "current_state": "unassigned",
  6.     "unassigned_info": {
  7.         "reason": "ALLOCATION_FAILED",
  8.         "at": "2019-03-13T11:53:43.385Z",
  9.         "failed_allocation_attempts": 5,
  10.         "details": "failed shard on node [d7RZ_TVwQpipnNIAXuqiGg]: failed recovery, failure RecoveryFailedException[[cpi_sensors_shipped][0]: Recovery failed on {threadripper-1}{d7RZ_TVwQpipnNIAXuqiGg}{TW3qKckzRm-BTsg3C1JepQ}{10.0.2.15}{10.0.2.15:9300}{ml.machine_memory=8376053760, xpack.installed=true, ml.max_open_jobs=20, ml.enabled=true}]; nested: IndexShardRecoveryException[failed recovery]; nested: TranslogCorruptedException[translog from source [/nas/elastic/elasticsearch/data/nodes/0/indices/TlrkkNKrRPGDdIiqaZvkBg/0/translog] is corrupted]; nested: FileSystemException[/nas/elastic/elasticsearch/data/nodes/0/indices/TlrkkNKrRPGDdIiqaZvkBg/0/translog/translog-14.tlog: Device or resource busy]; ",
  11.         "last_allocation_status": "no"
  12.     },
  13.     "can_allocate": "no",
  14.     "allocate_explanation": "cannot allocate because allocation is not permitted to any of the nodes that hold an in-sync shard copy",
  15.     "node_allocation_decisions": [
  16.         {
  17.             "node_id": "d7RZ_TVwQpipnNIAXuqiGg",
  18.             "node_name": "threadripper-1",
  19.             "transport_address": "10.0.2.15:9300",
  20.             "node_attributes": {
  21.                 "ml.machine_memory": "8376053760",
  22.                 "xpack.installed": "true",
  23.                 "ml.max_open_jobs": "20",
  24.                 "ml.enabled": "true"
  25.             },
  26.             "node_decision": "no",
  27.             "store": {
  28.                 "in_sync": true,
  29.                 "allocation_id": "KVWkUM8lRgaCvzh3xuUT_A"
  30.             },
  31.             "deciders": [
  32.                 {
  33.                     "decider": "max_retry",
  34.                     "decision": "NO",
  35.                     "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[2019-03-13T11:53:43.385Z], failed_attempts[5], delayed=false, details[failed shard on node [d7RZ_TVwQpipnNIAXuqiGg]: failed recovery, failure RecoveryFailedException[[cpi_sensors_shipped][0]: Recovery failed on {threadripper-1}{d7RZ_TVwQpipnNIAXuqiGg}{TW3qKckzRm-BTsg3C1JepQ}{10.0.2.15}{10.0.2.15:9300}{ml.machine_memory=8376053760, xpack.installed=true, ml.max_open_jobs=20, ml.enabled=true}]; nested: IndexShardRecoveryException[failed recovery]; nested: TranslogCorruptedException[translog from source [/nas/elastic/elasticsearch/data/nodes/0/indices/TlrkkNKrRPGDdIiqaZvkBg/0/translog] is corrupted]; nested: FileSystemException[/nas/elastic/elasticsearch/data/nodes/0/indices/TlrkkNKrRPGDdIiqaZvkBg/0/translog/translog-14.tlog: Device or resource busy]; ], allocation_status[deciders_no]]]"
  36.                 }
  37.             ]
  38.         }
  39.     ]
  40. }
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement