# While shard was relocating, experienced very high search response times

**URL:** <https://discuss.elastic.co/t/while-shard-was-relocating-experienced-very-high-search-response-times/22219>\
**Category:** Elasticsearch\
**Created:** [February 17, 2015, 9:45pm UTC](https://discuss.elastic.co/t/while-shard-was-relocating-experienced-very-high-search-response-times/22219 "2015-02-17T21:45:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nickcanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickcanz/32/44873_2.png) [@nickcanz](https://discuss.elastic.co/u/nickcanz)\
**Post date:** [February 17, 2015, 9:45pm UTC](https://discuss.elastic.co/t/while-shard-was-relocating-experienced-very-high-search-response-times/22219/1 "2015-02-17T21:45:21Z")

</div>

We use rolling daily indexes. After we deleted one, Elasticsearch decided  
to relocate a replica shard to another node. Totally fine, that's what I  
expect Elasticsearch to do.

What I didn't expect was for search queries that might have used that shard  
to bomb out. Writes to different indexes still performed fine, but searches  
either timed out or returned with very long response times. Once the shard  
completed relocating (15min for a 26gb shard), performance returned to  
normal.

We have all the logs and marvel data for this time period, and I don't see  
anything that seems out of the ordinary. What logs/settings I should be  
looking at so we don't have this problem again?

Thanks,

--  
Nick Canzoneri  
Developer, Wildbit [http://wildbit.com/](http://wildbit.com/)  
Beanstalk [http://beanstalkapp.com/](http://beanstalkapp.com/), Postmark [http://postmarkapp.com/](http://postmarkapp.com/),  
dploy.io

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKWm5yPfQ1dLW-QengDs6gxfP9bjhnH7q7qnR-kYnY7nZu8d\_g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKWm5yPfQ1dLW-QengDs6gxfP9bjhnH7q7qnR-kYnY7nZu8d_g%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 12:32am UTC](https://discuss.elastic.co/t/while-shard-was-relocating-experienced-very-high-search-response-times/22219/2 "2017-07-06T00:32:03Z")

</div>