# Experience with Elasticsearch on Openstack

**URL:** <https://discuss.elastic.co/t/experience-with-elasticsearch-on-openstack/60892>\
**Category:** Elasticsearch\
**Created:** [September 19, 2016, 1:32pm UTC](https://discuss.elastic.co/t/experience-with-elasticsearch-on-openstack/60892 "2016-09-19T13:32:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MartinG](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@MartinG](https://discuss.elastic.co/u/MartinG)\
**Post date:** [September 19, 2016, 1:32pm UTC](https://discuss.elastic.co/t/experience-with-elasticsearch-on-openstack/60892/1 "2016-09-19T13:32:11Z")

</div>

Hello,

Does somebody has experience with Elasticsearch on Openstack?

During our tests we notice that sometimes a node is freezed for some secondes when the Hypervisor has a problem and the node is moved to another Hypervisor.

In such cases the cluster status becomes "red" and there are always some shards unassigned. They can be assigned manually, but I would like to prevent this behaviour.

Does somebody notice a similar behaviour and was able to fix it? Maybe the connection or timeout parameters of ES can be changed to consider a freezed node in a cluster as "down".

Thanx in advance!

Greetings!

---

<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:19pm UTC](https://discuss.elastic.co/t/experience-with-elasticsearch-on-openstack/60892/2 "2017-07-05T22:19:09Z")

</div>

Closed on July 5, 2017, 10:19pm UTC