# Growing field mapping management

**URL:** <https://discuss.elastic.co/t/growing-field-mapping-management/245235>\
**Category:** Elasticsearch\
**Created:** [August 17, 2020, 12:35pm UTC](https://discuss.elastic.co/t/growing-field-mapping-management/245235 "2020-08-17T12:35:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![WDK](https://avatars.discourse-cdn.com/v4/letter/w/a87d85/32.png) [@WDK](https://discuss.elastic.co/u/WDK)\
**Post date:** [August 17, 2020, 12:35pm UTC](https://discuss.elastic.co/t/growing-field-mapping-management/245235/1 "2020-08-17T12:35:15Z")

</div>

Hi all,

I wonder how people here manage the growing amount of mappings you see in some indices. Especially kubernetes logs tend to have a wild variety of field. In my situation, all kubernetes logs end up in the same index (ILM'ed to 50GB) and we now have 4800+ field in the index pattern.

This is beginning to throw mapping conflicts and "request entity too large" when refreshing the index pattern.

What is the best way to go about managing this growing list? Keep smaller indices? Separate the k8s logs more? Maybe more specific index patterns instead of logstash\* ?

---

<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:** [September 14, 2020, 12:35pm UTC](https://discuss.elastic.co/t/growing-field-mapping-management/245235/2 "2020-09-14T12:35:44Z")

</div>

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