# Reindex + growing storage size

**URL:** <https://discuss.elastic.co/t/reindex-growing-storage-size/118502>\
**Category:** Elasticsearch\
**Created:** [February 5, 2018, 5:25pm UTC](https://discuss.elastic.co/t/reindex-growing-storage-size/118502 "2018-02-05T17:25:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mkovrigovich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mkovrigovich/32/27375_2.png) [@mkovrigovich](https://discuss.elastic.co/u/mkovrigovich)\
**Post date:** [February 5, 2018, 5:25pm UTC](https://discuss.elastic.co/t/reindex-growing-storage-size/118502/1 "2018-02-05T17:25:07Z")

</div>

Hi,  
in our system we do backups using reindex command with **wait\_for\_completion=true** like

```auto
    POST _reindex/?wait_for_completion=true
    {
      "source": {
        "index": "master_data"
      },
      "dest": {
        "index": "data_backup_timestamp"
      }
    }

```

then we populate the master table with new data

after that command I checked the backup index and got numer of docs in backup index the same as in the master index, that is ok.

if we run the following command manually a few times

```auto
GET _cat/indices/?v

```

we see the backup index store size is still growing, I wonder why?  
The thought is once reindex is completed then no actions are performed. Growing index is confusing to me a bit, so unsure if the backup has completed or still running  
Could you please explain that behavior?

Thank you in advance!

---

<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:** [March 5, 2018, 5:25pm UTC](https://discuss.elastic.co/t/reindex-growing-storage-size/118502/2 "2018-03-05T17:25:30Z")

</div>

Closed on March 5, 2018, 5:25pm UTC

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