# ES2.1 shard recovery is extremely slow

**URL:** <https://discuss.elastic.co/t/es2-1-shard-recovery-is-extremely-slow/36356>\
**Category:** Elasticsearch\
**Created:** [December 4, 2015, 8:51am UTC](https://discuss.elastic.co/t/es2-1-shard-recovery-is-extremely-slow/36356 "2015-12-04T08:51:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jochen\_st](https://avatars.discourse-cdn.com/v4/letter/j/c0e974/32.png) [@jochen\_st](https://discuss.elastic.co/u/jochen_st)\
**Post date:** [December 4, 2015, 10:17am UTC](https://discuss.elastic.co/t/es2-1-shard-recovery-is-extremely-slow/36356/2 "2015-12-04T10:17:08Z")

</div>

Please see also this thread:

> [@ES 2.1 shards stuck in translog recovery](https://discuss.elastic.co/t/es-2-1-shards-stuck-in-translog-recovery/35716):
>
> We are running ES 2.1 single node cluster on Windows 7 / NTFS. After ES crashed due to faulty disk (replacement is under way), the indices being written to at time of crash are stuck in translog recovery phase. I will use the .marvel index as example here. Output from curl -s "http://$ES\_HOST:9200/\_cat/recovery?v=h" index shard time type stage source\_host target\_host repository snapshot files files\_percent bytes bytes\_percent total\_files total\_bytes translog translog\_per…

---

_[View the full topic](https://discuss.elastic.co/t/es2-1-shard-recovery-is-extremely-slow/36356)._