# Mapper\_exception while using runtime dynamic mapping

**URL:** <https://discuss.elastic.co/t/mapper-exception-while-using-runtime-dynamic-mapping/343764>\
**Category:** Elasticsearch\
**Tags:** runtime-fields\
**Created:** [September 25, 2023, 1:13pm UTC](https://discuss.elastic.co/t/mapper-exception-while-using-runtime-dynamic-mapping/343764 "2023-09-25T13:13:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaykb77](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@jaykb77](https://discuss.elastic.co/u/jaykb77)\
**Post date:** [September 25, 2023, 1:13pm UTC](https://discuss.elastic.co/t/mapper-exception-while-using-runtime-dynamic-mapping/343764/1 "2023-09-25T13:13:49Z")

</div>

Hi,

We are using runtime dynamic mapping for indices and receiving below error while indexing.

```auto
Indexing failed for some events, type: mapper_exception, reason: timed out while waiting for a dynamic mapping update

```

Events have some default keys required by the system, however, events can also contain number of custom arbitrary keys added by users. Required keys are listed in the mapping directly, other keys are mapped in the runtime manner.

I can not find any errors within elasticsearch cluster logs. Any idea why this may be happening? Or what are some of the checks we can do to see why this is happening?

---

<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:** [October 23, 2023, 1:14pm UTC](https://discuss.elastic.co/t/mapper-exception-while-using-runtime-dynamic-mapping/343764/2 "2023-10-23T13:14:39Z")

</div>

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