Rollover very slow to occurr

[Ronaldo_Lanhellas]

I'm trying to apply the following policy with rollover:

` "policy": {
    "phases": {
      "hot":{
        "actions": {
          "rollover":{
            "max_size": "2GB"
          }
        }
      },
      "warm": {
        "min_age": "3d",
        "actions": {
          "forcemerge": {
            "max_num_segments": 1
          }
        }
      },
      "delete": {
        "min_age": "5d",
        "actions": {
          "delete": {}
        }
      }
    }
  }`

And now I have an index that has 4.4GB and Rollover don't happen yet, see:

As you can see Rollover started about 8h ago but not created yet as "-00002" index, and my original index "-000001" don't stop to grow up.

[warkolm (Mark Walkom)]

Can you share the output from GET /YOURINDEX-000001/_ilm/explain?

[Ronaldo_Lanhellas]

I already discovered the problem. I was in a loop, trying to create another index pointing to same alias with "write=true", but this is not possible. So, rolloved indexes can't have the "alias write=true" and now everything works fine.