# Rollover is never acknowledged

**URL:** <https://discuss.elastic.co/t/rollover-is-never-acknowledged/172197>\
**Category:** Elasticsearch\
**Created:** [March 13, 2019, 6:15pm UTC](https://discuss.elastic.co/t/rollover-is-never-acknowledged/172197 "2019-03-13T18:15:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lebra](https://avatars.discourse-cdn.com/v4/letter/l/e5b9ba/32.png) [@lebra](https://discuss.elastic.co/u/lebra)\
**Post date:** [March 13, 2019, 6:15pm UTC](https://discuss.elastic.co/t/rollover-is-never-acknowledged/172197/1 "2019-03-13T18:15:44Z")

</div>

For some reason my \_rollover calls never get acknowledged:

Index alias: logstash

```
POST logstash/_rollover
{
  "conditions": {
    "max_size": "43.7gb"
  }
}

```

Index info:

```
GET logstash/_settings
logstash/_settings?pretty
{
  "logstash-000002" : {
    "settings" : {
      "index" : {
        "allocation" : {
          "max_retries" : "10"
        },
        "mapping" : {
          "total_fields" : {
            "limit" : "2000"
          }
        },
        "refresh_interval" : "5s",
        "number_of_shards" : "1",
        "provided_name" : "logstash-000002",
        "creation_date" : "1548957055823",
        "number_of_replicas" : "1",
        "uuid" : "RtpxnugZQnKDpKr2QU13ew",
        "version" : {
          "created" : "6040299"
        }
      }
    }
  }
}

```

ES info:

```
{
  "name" : "ZAWRu-L",
  "cluster_name" : "569304875476:leo-perfect",
  "cluster_uuid" : "HYRo-SiLTZePoRCOdjtTVA",
  "version" : {
    "number" : "6.4.2",
    "build_flavor" : "oss",
    "build_type" : "zip",
    "build_hash" : "04711c2",
    "build_date" : "2018-10-16T09:16:35.059415Z",
    "build_snapshot" : false,
    "lucene_version" : "7.4.0",
    "minimum_wire_compatibility_version" : "5.6.0",
    "minimum_index_compatibility_version" : "5.0.0"
  },
  "tagline" : "You Know, for Search"
}
```

---

<div class="post-metadata">

**Author:** ![gbrown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gbrown/32/34482_2.png) [@gbrown](https://discuss.elastic.co/u/gbrown)\
**Post date:** [March 13, 2019, 10:21pm UTC](https://discuss.elastic.co/t/rollover-is-never-acknowledged/172197/2 "2019-03-13T22:21:31Z")

</div>

What size is the index `logstash-000002`? You can check by running:

```auto
GET _cat/indices/logstash-000002?v

```

Which will give you something that looks like:

```auto
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open testindex TRcknejsRUSkdz_UkDj-Xg 5 1 4 0 25.1kb 12.5kb

```

Rollover looks at the primary store size, shown above as the column `pri.store.size`, rather than the size including replicas (which is just `store.size`), and will only roll over if the index's primary store size is greater than the `max_size` parameter in the rollover request (or if any other provided conditions match).

---

<div class="post-metadata">

**Author:** ![lebra](https://avatars.discourse-cdn.com/v4/letter/l/e5b9ba/32.png) [@lebra](https://discuss.elastic.co/u/lebra)\
**Post date:** [March 13, 2019, 11:48pm UTC](https://discuss.elastic.co/t/rollover-is-never-acknowledged/172197/3 "2019-03-13T23:48:37Z")

</div>

@gbrown Thanks for the clarification.

As soon as I made the necessary modifications, the index rolled over 😅

```
GET _cat/indices?v
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open logstash-000002 RtpxnugZQnKDpKr2QU13ew 1 1 198581920 0 43.8gb 22gb
green open logstash-000001 aEqNz95YRsm08rEfeB4d_A 1 1 145875 0 60mb 30mb
green open logstash-000003 k3xEAF2kR4yH92QG-O4Log 1 1 0 0 522b 261b
```

---

<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:** [April 10, 2019, 11:53pm UTC](https://discuss.elastic.co/t/rollover-is-never-acknowledged/172197/4 "2019-04-10T23:53:23Z")

</div>

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