# How to prevent performance degradation while recovery

**URL:** <https://discuss.elastic.co/t/how-to-prevent-performance-degradation-while-recovery/9234>\
**Category:** Elasticsearch\
**Created:** [October 3, 2012, 8:17pm UTC](https://discuss.elastic.co/t/how-to-prevent-performance-degradation-while-recovery/9234 "2012-10-03T20:17:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jae](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jae/32/791_2.png) [@Jae](https://discuss.elastic.co/u/Jae)\
**Post date:** [October 3, 2012, 8:17pm UTC](https://discuss.elastic.co/t/how-to-prevent-performance-degradation-while-recovery/9234/1 "2012-10-03T20:17:08Z")

</div>

ElasticSearch is very awesome, but I really really want ElasticSearch to be  
more robust with recovery situation.

Today, 2 elasticsearch instances were down. (don't worry, servers were  
rebooted by AWS) and cluster status was gone to yellow.

The problem was, a lot of bulk index requests were dropped due to timeout  
with 10s.

Is there anybody who knows how to mitigate this problem such as parameter  
values?

Would it be better if I change c.r.a parameters? If so, what would be  
tuning values?

Thank you  
Best, Jae

--

---

<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 6, 2017, 3:10am UTC](https://discuss.elastic.co/t/how-to-prevent-performance-degradation-while-recovery/9234/2 "2017-07-06T03:10:17Z")

</div>

Closed on July 6, 2017, 3:10am UTC