# Cluster load while updating mappings of live production indexes

**URL:** <https://discuss.elastic.co/t/cluster-load-while-updating-mappings-of-live-production-indexes/293718>\
**Category:** Elasticsearch\
**Created:** [January 7, 2022, 9:29am UTC](https://discuss.elastic.co/t/cluster-load-while-updating-mappings-of-live-production-indexes/293718 "2022-01-07T09:29:17Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ginopino](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ginopino/32/99954_2.png) [@ginopino](https://discuss.elastic.co/u/ginopino)\
**Post date:** [January 7, 2022, 9:29am UTC](https://discuss.elastic.co/t/cluster-load-while-updating-mappings-of-live-production-indexes/293718/1 "2022-01-07T09:29:17Z")

</div>

Hello!  
I need to add a couple of new `keyword` fields to a significant quantity of production indexes which are using a mapping with `dynamic: strict`  
I was hoping to be able to use a wildcard with the update mapping API, something like

```auto
PUT /my-index-prefix-*/_mapping
{
  "properties": {
    "email": {
      "type": "keyword"
    }
  }
}

```

I am concerned about the safety of running this against heavily used production indexes. Should I expect some kind of impact on the cluster performance while the mappings are updated?

thanks

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 9, 2022, 9:56pm UTC](https://discuss.elastic.co/t/cluster-load-while-updating-mappings-of-live-production-indexes/293718/2 "2022-01-09T21:56:36Z")

</div>

Welcome to our community! 😃

Yes, there is a cost to doing this, so it'll likely impact your cluster traffic.

---

<div class="post-metadata">

**Author:** ![ginopino](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ginopino/32/99954_2.png) [@ginopino](https://discuss.elastic.co/u/ginopino)\
**Post date:** [January 10, 2022, 9:39am UTC](https://discuss.elastic.co/t/cluster-load-while-updating-mappings-of-live-production-indexes/293718/3 "2022-01-10T09:39:26Z")

</div>

Hi Mark, thank you for your answer!  
Is there a recommended way for doing this while minimizing the performance impact? Maybe applying updates to one index at a time instead of using a wildcard update?  
Or it's better to create new indexes with the updated mapping and then perform a reindex?

many thanks

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 10, 2022, 9:50pm UTC](https://discuss.elastic.co/t/cluster-load-while-updating-mappings-of-live-production-indexes/293718/4 "2022-01-10T21:50:34Z")

</div>

I'd start by doing a few, and then seeing what sort of impact it has.  
Ultimately it'll depend on how many indices are being updated.

---

<div class="post-metadata">

**Author:** ![ginopino](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ginopino/32/99954_2.png) [@ginopino](https://discuss.elastic.co/u/ginopino)\
**Post date:** [January 16, 2022, 6:14pm UTC](https://discuss.elastic.co/t/cluster-load-while-updating-mappings-of-live-production-indexes/293718/5 "2022-01-16T18:14:38Z")

</div>

ok, thanks I'll give it a try!

---

<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:** [February 13, 2022, 6:15pm UTC](https://discuss.elastic.co/t/cluster-load-while-updating-mappings-of-live-production-indexes/293718/6 "2022-02-13T18:15:34Z")

</div>

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