# Elasticseach index problem - closing randomly

**URL:** https://discuss.elastic.co/t/elasticseach-index-problem-closing-randomly/143917
**Category:** Elasticsearch
**Created:** [August 10, 2018, 6:03pm UTC](https://discuss.elastic.co/t/elasticseach-index-problem-closing-randomly/143917 "2018-08-10T18:03:28Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Sanj\_Gunetileke](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@Sanj\_Gunetileke](https://discuss.elastic.co/u/Sanj_Gunetileke)
#### Post date: [August 10, 2018, 6:03pm UTC](https://discuss.elastic.co/t/elasticseach-index-problem-closing-randomly/143917/1 "2018-08-10T18:03:28Z")

</div>

Hello,  
I have a node with 3 indexes and each index has 3 shards. Total disk usage is about 9GB.  
OS: Windows server 2016 (virtual machine)  
ES: 6.2.4  
memory: 16GB  
HD: 250GB.  
Virusscanner: mcafee.

Some indexes close by itself at random times. I have to open these indexes by using the open command. Is there a reason why the indexes close by itself.  
Is there a setting I can use to prevent the indexes closing?  
Thanks in advance.  
Sanj

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [August 10, 2018, 8:26pm UTC](https://discuss.elastic.co/t/elasticseach-index-problem-closing-randomly/143917/2 "2018-08-10T20:26:52Z")

</div>

You probably have something which runs and close the indices.  
May be you are using curator or something?  
Or someone has access to your cluster?

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [August 10, 2018, 8:49pm UTC](https://discuss.elastic.co/t/elasticseach-index-problem-closing-randomly/143917/3 "2018-08-10T20:49:35Z")

</div>

There is no way Elasticsearch can just close an index, or an index can just close itself, someone has to request it.

---

<div class="post-metadata">

### Author: ![Sanj\_Gunetileke](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@Sanj\_Gunetileke](https://discuss.elastic.co/u/Sanj_Gunetileke)
#### Post date: [August 10, 2018, 9:50pm UTC](https://discuss.elastic.co/t/elasticseach-index-problem-closing-randomly/143917/4 "2018-08-10T21:50:42Z")

</div>

Is there a log setting to give more explanation of who is sending the close command? Or increase the log detail level?

---

<div class="post-metadata">

### Author: ![Sanj\_Gunetileke](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@Sanj\_Gunetileke](https://discuss.elastic.co/u/Sanj_Gunetileke)
#### Post date: [August 10, 2018, 9:51pm UTC](https://discuss.elastic.co/t/elasticseach-index-problem-closing-randomly/143917/5 "2018-08-10T21:51:57Z")

</div>

Is there a setting to disable index closing?

---

<div class="post-metadata">

### Author: ![Sanj\_Gunetileke](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@Sanj\_Gunetileke](https://discuss.elastic.co/u/Sanj_Gunetileke)
#### Post date: [August 14, 2018, 9:37pm UTC](https://discuss.elastic.co/t/elasticseach-index-problem-closing-randomly/143917/6 "2018-08-14T21:37:38Z")

</div>

I got around this by setting the index close option to false. So the index will never close. This has helped me.

---

<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: [September 11, 2018, 9:37pm UTC](https://discuss.elastic.co/t/elasticseach-index-problem-closing-randomly/143917/7 "2018-09-11T21:37:53Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
