# Cannot get curator to rollover an index

**URL:** <https://discuss.elastic.co/t/cannot-get-curator-to-rollover-an-index/130031>\
**Category:** Elasticsearch\
**Created:** [April 30, 2018, 1:55pm UTC](https://discuss.elastic.co/t/cannot-get-curator-to-rollover-an-index/130031 "2018-04-30T13:55:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [April 30, 2018, 1:55pm UTC](https://discuss.elastic.co/t/cannot-get-curator-to-rollover-an-index/130031/1 "2018-04-30T13:55:51Z")

</div>

I have a feeling there is going to be a forehead slapping moment here, but anyways... I am trying to rollover indexes based on size, and I cannot get it to work. The alias name I want to rollover is logstash-production, and 'GET \_alias/logstash-production' shows there is an index with that alias.

```auto
{
  "logstash-production-000001": {
    "aliases": {
      "logstash-production": {}
    }
  }
}

```

The curator configuration includes

```auto
  1:
    action: rollover
    description: >-
      Rollover production samples every 1 GB
    options:
      name: logstash-production
      conditions:
        max_size: 1gb
      extra_settings:
        index.number_of_shards: 2
        index.number_of_replicas: 0

```

As of this morning the index is 4.9 GB. I set the loglevel to DEBUG and blacklist: [] and all I get when curator runs is this. None of the voluminous output I get when my aged-based yml is run.

```auto
2018-04-30 09:45:02,119 DEBUG curator.cli run:108 Client and logging options validated.
2018-04-30 09:45:02,119 DEBUG curator.cli run:112 default_timeout = 30
2018-04-30 09:45:02,119 DEBUG curator.cli run:116 action_file: /home/elasticsearch/.curator/rolloverIndices.yml

```

elasticsearch 6.2.3, curator 5.5.1.

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [April 30, 2018, 3:05pm UTC](https://discuss.elastic.co/t/cannot-get-curator-to-rollover-an-index/130031/2 "2018-04-30T15:05:52Z")

</div>

If it's stopping there, it is likely that there is something misformatted in your YAML file. It's attempting to read the file, and not able to go farther.

Perhaps put in the entire YAML config file here, and we can look it over. Double-check the indentation and colons and all that formatting stuff.

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [April 30, 2018, 3:20pm UTC](https://discuss.elastic.co/t/cannot-get-curator-to-rollover-an-index/130031/3 "2018-04-30T15:20:58Z")

</div>

> [@theuntergeek](#):
>
> If it's stopping there, it is likely that there is something misformatted in your YAML file.

Yes, index.number\_of\_replicas is indented by 8 spaces, and vim had auto-indented it using a tab. It is now working. Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 28, 2018, 3:21pm UTC](https://discuss.elastic.co/t/cannot-get-curator-to-rollover-an-index/130031/4 "2018-05-28T15:21:03Z")

</div>

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