IndexLifecycleRunner policy index failed on step IllegalArgumentException is not the write index for alias

ElasticSearch (7.7) seems to be in confusion about which indices it has rolled over and is logging:

[2020-06-02T09:23:53,425][ERROR][o.e.x.i.IndexLifecycleRunner] [ecom-repository01] policy [test-policy] for index [logs-test-000001] failed on step [{"phase":"hot","action":"rollover","name":"check-rollover-ready"}]. Moving to ERROR step
java.lang.IllegalArgumentException: index [logs-test-000001] is not the write index for alias [logs-test]

As you can see below it should not be rolling logs-test-000001 over but logs-000003:

[
    {
        "alias": "logs-test",
        "index": "logs-test-000003",
        "filter": "-",
        "routing.index": "-",
        "routing.search": "-",
        "is_write_index": "true"
    },
    {
        "alias": "logs-test",
        "index": "logs-test-000002",
        "filter": "-",
        "routing.index": "-",
        "routing.search": "-",
        "is_write_index": "false"
    },
    {
        "alias": "logs-test",
        "index": "logs-test1",
        "filter": "-",
        "routing.index": "-",
        "routing.search": "-",
        "is_write_index": "false"
    },
    {
        "alias": "logs-test",
        "index": "logs-test-000001",
        "filter": "-",
        "routing.index": "-",
        "routing.search": "-",
        "is_write_index": "false"
    }
]

How can we point ILM at the correct index??

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