# Elasticsearch index creation high master timeout causing index creation retries internally

**URL:** <https://discuss.elastic.co/t/elasticsearch-index-creation-high-master-timeout-causing-index-creation-retries-internally/51133>\
**Category:** Elasticsearch\
**Created:** [May 27, 2016, 8:42am UTC](https://discuss.elastic.co/t/elasticsearch-index-creation-high-master-timeout-causing-index-creation-retries-internally/51133 "2016-05-27T08:42:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![akgoel-mo](https://avatars.discourse-cdn.com/v4/letter/a/9de053/32.png) [@akgoel-mo](https://discuss.elastic.co/u/akgoel-mo)\
**Post date:** [May 27, 2016, 8:42am UTC](https://discuss.elastic.co/t/elasticsearch-index-creation-high-master-timeout-causing-index-creation-retries-internally/51133/1 "2016-05-27T08:42:22Z")

</div>

Hello everyone

I am facing a weird problem with elasticsearch. I am running ES 1.4.1 on 32G (16G heap) data nodes(19) along with 64G (32G heap) master nodes(3). My cluster metadata has grown too much causing all master operations to be slow. Even a 64G master is not able to cope up well. Due to this any new index creations are failing very frequently.

I am trying to forcibly create these indices by giving a **very high master\_timeout** (10000 sec). My request is returning, but I am seeing index creation failure logs on master. As soon as an attempt to create the index fails, I see **another task in master's pending\_tasks** to create the same index. This keeps happening till the master\_timeout value.

Is there an internal retry mechanism in elasticsearch, which is kicking in here? I was under the impression that one task will be tried only once and if failed, will return a failure.

This retry mechanism is queueing up tasks on master affecting my overall system performance. Is there a way to flush the master pending tasks or to disable this index creation retry? Has anyone faced such a scenario earlier?

Any info on this will be greatly helpful. Looking forward to the support from the ES community.

Thanks  
Akshay Goel

---

<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:** [May 29, 2016, 1:12am UTC](https://discuss.elastic.co/t/elasticsearch-index-creation-high-master-timeout-causing-index-creation-retries-internally/51133/2 "2016-05-29T01:12:57Z")

</div>

1. Upgrade
2. Fix the massive cluster state problems

Anything else is just going to waste your time.

---

<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:** [July 5, 2017, 10:48pm UTC](https://discuss.elastic.co/t/elasticsearch-index-creation-high-master-timeout-causing-index-creation-retries-internally/51133/3 "2017-07-05T22:48:18Z")

</div>