Rollover illegal_state_exception and illegal_argument_exception

Elastic Stack Elasticsearch
1

I implemented rollover index myapp ant it works like a charm for a long time. Today, I find out in Kibana that two of my indices encounter errors: 2 indices have lifecycle errors.

GET /_cat/aliases/myapp?v=true
alias index                 filter routing.index routing.search
myapp rollover-myapp-000014 -      -             -
myapp rollover-myapp-000015 -      -             -
myapp rollover-myapp-000025 -      -             -
myapp rollover-myapp-000026 -      -             -
myapp rollover-myapp-000027 -      -             -

rollover-myapp-000014: Index lifecycle error

illegal_state_exception: no rollover info found for [rollover-myapp-000014] with alias [myapp], the index has not yet rolled over with that alia

rollover-myapp-000015: Index lifecycle error
illegal_argument_exception: index [myapp] is not the write index for alias [rollover-myapp-000015]

The rollover process continues without problem, there were created more rollover indices and currently there were 25 and 26. I forced rollover with rollover api and create 27 just to be sure, no more errors will occur - it is ok.

QUESTIONS:

  1. what this errors means, why this errors occours and why the rollover process continuous without problem?
  2. how can I fix this indices to be managed by ILM?

Sometimes, rollover indices are stucked but retry lifecycle step can fix it immediatelly.

I found similar issue here:

POST _ilm/move/my-index-000001
{
  "current_step": { 
    "phase": "hot",
    "action": "rollover",
    "name": "ERROR"
  },
  "next_step": { 
    "phase": "hot",
    "action": "rollover",
    "name": "set-indexing-complete"
  }
}

But I am not sure what name key in current_step and next_step means. I tried it:

POST _ilm/move/rollover-myapp-000014
{
  "current_step": { 
    "phase": "hot",
    "action": "rollover",
    "name": "ERROR"
  },
  "next_step": { 
    "phase": "warm",
    "action": "forcemerge",
    "name": "set-indexing-complete"
  }
}

I have warm phase in my-rollover policy but ends up with error:

{
  "error": {
    "root_cause": [
      {
        "type": "remote_transport_exception",
        "reason": "[elasticsearch][10.0.7.231:9300][cluster:admin/ilm/_move/post]"
      }
    ],
    "type": "illegal_argument_exception",
    "reason": "step [{\"phase\":\"warm\",\"action\":\"forcemerge\",\"name\":\"set-indexing-complete\"}] for index [rollover-myapp-000014] with policy [my-rollover] does not exist"
  },
  "status": 400
}

Elasticsearch: v6.7.1

2

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