Curator Rollover ignores max_docs condition


(Peter Bøndum) #1

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


(Aaron Mildenstein) #2

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.


(Peter Bøndum) #3

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


(Aaron Mildenstein) #4

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


(Peter Bøndum) #5

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

Thanks


(system) #6

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