Question about roll-over behavior

Plugins Index Management
1

I noticed something funny today. I converted one of our biggest indices (1TB daily) to a rollover policy finally, i named it “logs-00000001”, when the first roll-over came about after 100G of data I now see “logs-000002” (1 less 0), is this something configurable? I guess it doesn’t matter in the short term but it made me wonder, what happens at “logs-999999” ? does it start back at “logs-000001” ?
Thanks.

2

This is something Elasticsearch does natively, unrelated to ISM. You can also see by doing a quick test of creating test-01 and rolling it over manually and it’ll create a new index with test-00001

e.g.

{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "old_index" : "testing-01",
  "new_index" : "testing-000002",
  "rolled_over" : true,
  "dry_run" : false,
  "conditions" : { }
}

As for what happens at 999999… I don’t know :stuck_out_tongue: let’s see…

{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "old_index" : "rollover-999997",
  "new_index" : "rollover-999998",
  "rolled_over" : true,
  "dry_run" : false,
  "conditions" : { }
}

{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "old_index" : "rollover-999998",
  "new_index" : "rollover-999999",
  "rolled_over" : true,
  "dry_run" : false,
  "conditions" : { }
}

{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "old_index" : "rollover-999999",
  "new_index" : "rollover-1000000",
  "rolled_over" : true,
  "dry_run" : false,
  "conditions" : { }
}

{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "old_index" : "rollover-1000000",
  "new_index" : "rollover-1000001",
  "rolled_over" : true,
  "dry_run" : false,
  "conditions" : { }
}

Seems like it will just keep increasing.

1 Like