# Options to repair elasticsearch when BulkResponse hangs

**URL:** <https://discuss.elastic.co/t/options-to-repair-elasticsearch-when-bulkresponse-hangs/44863>\
**Category:** Elasticsearch\
**Created:** [March 18, 2016, 8:13pm UTC](https://discuss.elastic.co/t/options-to-repair-elasticsearch-when-bulkresponse-hangs/44863 "2016-03-18T20:13:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tartale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tartale/32/12162_2.png) [@tartale](https://discuss.elastic.co/u/tartale)\
**Post date:** [March 18, 2016, 8:13pm UTC](https://discuss.elastic.co/t/options-to-repair-elasticsearch-when-bulkresponse-hangs/44863/1 "2016-03-18T20:13:33Z")

</div>

I have a customer instance of elasticsearch 1.5.2 where a Java client process (using the Java API) is consistently experiencing a thread hang. The client process is using an ES transport client, and issuing a BulkRequest. The thread appears to be blocked in the following call:

BulkResponse bulkResponse = (BulkResponse) response.actionGet();

This may be distantly related to the following issue (which should've been fixed in 1.5.2):

> <https://github.com/elastic/elasticsearch/issues/1839>

I have a single-node elasticsearch server instance running on Windows Server 2008, so relocating of a shard is probably not a culprit.

If indeed there is some issue with the ES file system, however, what are my choices to repair the elasticsearch instance, and what can I look for to extract more evidence? The elasticsearch logs (both server and client) are in debug mode, and there's nothing immediate standing out.

---

<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, 11:07pm UTC](https://discuss.elastic.co/t/options-to-repair-elasticsearch-when-bulkresponse-hangs/44863/2 "2017-07-05T23:07:02Z")

</div>