Curator Rollover ignores max_docs condition

[pbmsys (Peter Bøndum)]

Hi.

I have setup a curator job to rollover my index every 2.000.000 docs. But curator keeps making the rollover every 1.000.000 docs.

My action file:

actions:
  1:
    action: rollover
    description: "Rollover the index associated with alias 'active-logs'"
    options:
      disable_action: false
      name: active-logs
      conditions:
        max_docs: 2000000
      continue_if_exception: False
      timeout_override:

any idea why this is happening

/Peter

[theuntergeek (Aaron Mildenstein)]

Curator is only forwarding the API call. What do you see if you send this in Console or curl?

Also, I believe that Elasticsearch counts all copies of your documents, so replicas make a difference to the count. 2,000,000 would be 1,000,000 if you have 1 replica shard.

[pbmsys (Peter Bøndum)]

@theuntergeek That makes perfect sense. We have 1 replica shard on the specific index.
Thank you very much

[theuntergeek (Aaron Mildenstein)]

It's not supposed to do that, of course, but for now it is. See this issue.

[pbmsys (Peter Bøndum)]

I will just subscribe to the issue so we don't get caught in creating doubled indexes after an upgrade

Thanks