# \[reindexing\] my\_index is much more larger after a re\_indexing

**URL:** <https://discuss.elastic.co/t/reindexing-my-index-is-much-more-larger-after-a-re-indexing/184726>\
**Category:** Elasticsearch\
**Created:** [June 7, 2019, 9:22am UTC](https://discuss.elastic.co/t/reindexing-my-index-is-much-more-larger-after-a-re-indexing/184726 "2019-06-07T09:22:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Derrar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/derrar/32/47708_2.png) [@Derrar](https://discuss.elastic.co/u/Derrar)\
**Post date:** [June 7, 2019, 9:22am UTC](https://discuss.elastic.co/t/reindexing-my-index-is-much-more-larger-after-a-re-indexing/184726/1 "2019-06-07T09:22:45Z")

</div>

Hello Everyone, I encounter the following issue: my\_index is much more larger after a re\_indexing and I've no idea why.

What I want to do:

- do a simple reindexing, keeping the same mapping, the destination index has 1 shards and 0 replicas.

Here is what I've done so far:

```auto
PUT /_template/filebeat_clone2
{
  "version": 1,
  "index_patterns": ["filebeat_clone2"],
  "order": 0,
  "settings": {
    "index": {
      "number_of_shards": "1",
      "number_of_replicas": "0",
      "refresh_interval": "5s"
    }
  }
}

POST _reindex?wait_for_completion=false
{
  "source": {
    "index": "filebeat-7.0.1-2019.05.13-000001"
  },
  "dest": {
    "index": "filebeat_clone2"
  }
}

GET _cat/indices/filebeat_clone,filebeat_clone2,filebeat-7.0.1-2019.05.13-000001?v&h=index,store.size,docs.count
index store.size docs.count
filebeat_clone2 107.9mb 366089
filebeat_clone 108.1mb 366089
filebeat-7.0.1-2019.05.13-000001 69.7mb 366089

GET filebeat-7.0.1-2019.05.13-000001/_settings
GET filebeat_clone/_settings
GET filebeat_clone2/_settings

GET _cat/shards/filebeat_clone,filebeat_clone2,filebeat-7.0.1-2019.05.13-000001?v
index shard prirep state docs store ip node
filebeat_clone 0 p STARTED 366089 108.1mb 192.168.63.15 cv0tlielaspoc
filebeat-7.0.1-2019.05.13-000001 0 p STARTED 366089 69.7mb 192.168.63.15 cv0tlielaspoc
filebeat_clone2 0 p STARTED 366089 107.9mb 192.168.63.15 cv0tlielaspoc

```

For some reason the two test indices have a larger size 😕

Any advice?

Thanks in advance for you help,  
kr,  
Derrar.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 7, 2019, 9:50am UTC](https://discuss.elastic.co/t/reindexing-my-index-is-much-more-larger-after-a-re-indexing/184726/2 "2019-06-07T09:50:54Z")

</div>

A first guess is that the mapping is not the same.

I think that if you call your index `filebeat-7.0.1-clone` instead of `filebeat_clone` it might apply the same index template as you have in `filebeat-7.0.1-2019.05.13-000001`.

---

<div class="post-metadata">

**Author:** ![Derrar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/derrar/32/47708_2.png) [@Derrar](https://discuss.elastic.co/u/Derrar)\
**Post date:** [June 7, 2019, 9:57am UTC](https://discuss.elastic.co/t/reindexing-my-index-is-much-more-larger-after-a-re-indexing/184726/3 "2019-06-07T09:57:22Z")

</div>

Thanks a lot 👍

```auto
GET _cat/indices/filebeat-7.0.1-clone,filebeat-7.0.1-2019.05.13-000001?v&h=index,store.size,docs.count
index store.size docs.count
filebeat-7.0.1-clone 69.7mb 366089
filebeat-7.0.1-2019.05.13-000001 69.7mb 366089

```

It won't happen in production as I'will use a template with settings and mapping, I assume I just took the wrong use-case for my test. Thanks again for your quick answer.

kr,  
Derrar.

nb: this post can be closed

---

<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:** [July 5, 2019, 9:57am UTC](https://discuss.elastic.co/t/reindexing-my-index-is-much-more-larger-after-a-re-indexing/184726/4 "2019-07-05T09:57:22Z")

</div>

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