# Index is larger after Re-index (6.6.1 to 7)

**URL:** <https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755>\
**Category:** Elasticsearch\
**Created:** [July 3, 2019, 3:02pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755 "2019-07-03T15:02:57Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![SCL\_ADMIN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scl_admin/32/49037_2.png) [@SCL\_ADMIN](https://discuss.elastic.co/u/SCL_ADMIN)\
**Post date:** [July 3, 2019, 3:02pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/1 "2019-07-03T15:02:57Z")

</div>

I'm making my way thought reindexing the indices from 6.6.1 to 7 but i'm noticing that the re-indexed index file is larger than the original.

also as part of the re-index the Mapping type has been changed to \_doc.

1. is changing the mapping type \_doc makes a difference?
2. Is there a way of reducing the size of the re-indexed index?

many thanks

---

<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:** [July 3, 2019, 3:41pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/2 "2019-07-03T15:41:25Z")

</div>

Is the mapping strictly identical? Can you share it in both cases?  
Did you try a `_forcemerge` on both indices?  
Could you run:

```auto
GET /_cat/indices/YOURINDEXNAME?v

```

on both clusters?

---

<div class="post-metadata">

**Author:** ![SCL\_ADMIN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scl_admin/32/49037_2.png) [@SCL\_ADMIN](https://discuss.elastic.co/u/SCL_ADMIN)\
**Post date:** [July 3, 2019, 3:55pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/3 "2019-07-03T15:55:59Z")

</div>

> [@dadoonet](#):
>
> GET /\_cat/indices/

I ran the command and got back:

```
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
yellow open reindexed-v7-filebeat-6.6.1-2019.03.15 rEBcwXB6Rsixj1F3Hs7X_w 5 1 2155531 0 1022.5mb 1022.5mb

```

this is a result of an in an upgrade process using kibana under the upgrade assistant.

also I have one machine in the cluster, so I would expect the health status to be yellow

---

<div class="post-metadata">

**Author:** ![SCL\_ADMIN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scl_admin/32/49037_2.png) [@SCL\_ADMIN](https://discuss.elastic.co/u/SCL_ADMIN)\
**Post date:** [July 3, 2019, 3:58pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/4 "2019-07-03T15:58:52Z")

</div>

> [@dadoonet](#):
>
> `_forcemerge`

no i didn't try this

---

<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:** [July 3, 2019, 4:34pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/5 "2019-07-03T16:34:04Z")

</div>

And what is the mapping for `reindexed-v7-filebeat-6.6.1-2019.03.15` and the mapping for `filebeat-6.6.1-2019.03.15`?

Also what is the output of:

```auto
GET /_cat/indices/filebeat-6.6.1-2019.03.15?v

```

---

<div class="post-metadata">

**Author:** ![SCL\_ADMIN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scl_admin/32/49037_2.png) [@SCL\_ADMIN](https://discuss.elastic.co/u/SCL_ADMIN)\
**Post date:** [July 4, 2019, 9:35am UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/6 "2019-07-04T09:35:08Z")

</div>

> [@dadoonet](#):
>
> GET /\_cat/indices/filebeat-6.6.1-2019.03.15?v

there isn't an one it's now the alias. refers back to the re-indexed copy

---

<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:** [July 4, 2019, 1:27pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/7 "2019-07-04T13:27:45Z")

</div>

So what was the concrete index name?

---

<div class="post-metadata">

**Author:** ![SCL\_ADMIN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scl_admin/32/49037_2.png) [@SCL\_ADMIN](https://discuss.elastic.co/u/SCL_ADMIN)\
**Post date:** [July 4, 2019, 2:34pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/8 "2019-07-04T14:34:02Z")

</div>

> [@dadoonet](#):
>
> concrete name

reindexed-v7-filebeat-6.6.1-2019.03.15

---

<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:** [July 4, 2019, 3:51pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/9 "2019-07-04T15:51:48Z")

</div>

What was the concrete index name for the source?

---

<div class="post-metadata">

**Author:** ![SCL\_ADMIN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scl_admin/32/49037_2.png) [@SCL\_ADMIN](https://discuss.elastic.co/u/SCL_ADMIN)\
**Post date:** [July 4, 2019, 4:10pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/10 "2019-07-04T16:10:36Z")

</div>

> [@SCL\_ADMIN](#):
>
> -filebeat-6.6.1-2019.03.15

filebeat-6.6.1-2019.03.15

the source index is gone after the reindex

please note I am using the Upgrade Assistant to do the reindex

---

<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:** [July 4, 2019, 4:29pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/11 "2019-07-04T16:29:14Z")

</div>

I see.

Can you remember exactly what was its size?

---

<div class="post-metadata">

**Author:** ![SCL\_ADMIN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scl_admin/32/49037_2.png) [@SCL\_ADMIN](https://discuss.elastic.co/u/SCL_ADMIN)\
**Post date:** [July 4, 2019, 4:34pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/12 "2019-07-04T16:34:43Z")

</div>

off the top of my head it was 750-800mb...

---

<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:** [July 4, 2019, 5:05pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/13 "2019-07-04T17:05:30Z")

</div>

Do you still have other indices which you did not migrate yet?

---

<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:** [August 1, 2019, 5:05pm UTC](https://discuss.elastic.co/t/index-is-larger-after-re-index-6-6-1-to-7/188755/14 "2019-08-01T17:05:34Z")

</div>

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