# Mapping update timeout when doing shard recovering

**URL:** <https://discuss.elastic.co/t/mapping-update-timeout-when-doing-shard-recovering/174036>\
**Category:** Elasticsearch\
**Created:** [March 27, 2019, 3:34am UTC](https://discuss.elastic.co/t/mapping-update-timeout-when-doing-shard-recovering/174036 "2019-03-27T03:34:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![shjdwxy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shjdwxy/32/43102_2.png) [@shjdwxy](https://discuss.elastic.co/u/shjdwxy)\
**Post date:** [March 27, 2019, 3:34am UTC](https://discuss.elastic.co/t/mapping-update-timeout-when-doing-shard-recovering/174036/1 "2019-03-27T03:34:13Z")

</div>

hi, guys  
We use Elasticsearch as log management solution. In daily operation, we often encounter this problem: "mapping update timeout occurred when logs of shard were recovering, so index speed was reduced ". When this happened, we have to set `cluster.routing.allocation.node_concurrent_recoveries` to 0, then mapping update succeed.  
I am wandering "what is the relationship between mapping update and shard recovering" ?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [March 27, 2019, 8:13am UTC](https://discuss.elastic.co/t/mapping-update-timeout-when-doing-shard-recovering/174036/2 "2019-03-27T08:13:32Z")

</div>

> [@shjdwxy](#):
>
> I am wandering "what is the relationship between mapping update and shard recovering" ?

Both of these operations involve the master node. From your description it sounds like your master node is overloaded. What does `GET _cluster/health` report?

---

<div class="post-metadata">

**Author:** ![shjdwxy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shjdwxy/32/43102_2.png) [@shjdwxy](https://discuss.elastic.co/u/shjdwxy)\
**Post date:** [March 28, 2019, 8:22am UTC](https://discuss.elastic.co/t/mapping-update-timeout-when-doing-shard-recovering/174036/4 "2019-03-28T08:22:05Z")

</div>

The cluster is in green or yellow status. Next time I will list the \_cluster/health output.

why the master node is involved when shard recovering ? The global cluster status is updated during recovering?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [March 28, 2019, 8:45am UTC](https://discuss.elastic.co/t/mapping-update-timeout-when-doing-shard-recovering/174036/5 "2019-03-28T08:45:54Z")

</div>

> [@shjdwxy](#):
>
> why the master node is involved when shard recovering ? The global cluster status is updated during recovering?

Yes, the cluster state is adjusted in order to start the recovery, and then again to indicate that recovery has completed and the shard is ready to serve searches.

---

<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:** [April 25, 2019, 8:45am UTC](https://discuss.elastic.co/t/mapping-update-timeout-when-doing-shard-recovering/174036/6 "2019-04-25T08:45:56Z")

</div>

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