# Just Pushed: Close and Open an index **URL:** \ **Category:** Elasticsearch\ **Created:** [October 23, 2010, 7:56pm UTC](https://discuss.elastic.co/t/just-pushed-close-and-open-an-index/3468 "2010-10-23T19:56:11Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 23, 2010, 7:56pm UTC](https://discuss.elastic.co/t/just-pushed-close-and-open-an-index/3468/1 "2010-10-23T19:56:11Z")
Hi, Just pushed support for closing and opening an index. Closing an index results in the index having almost no overhead on the cluster (except for maintaing its metadata). For this to happen, there has been a round of enhancements in elasticsearch, where if a node does not have a shards for a specific index allocated on it, it also closes that index (not metadata), which include parsed mappings, analyzers and other index level constructs. These enhancements, of course, apply for open indices as well, if a node has no shards for a specific index allocated on it. The fact that an index is closed is maintained across cluster restarts. A closed index will remain closed post full cluster restart. The state of an index (closed or opened) is exposed in the cluster state API. A closed index has no shards hence no shards allocation, so it will not be seen in the routing table. The issue is here: [http://github.com/elasticsearch/elasticsearch/issues/issue/447](http://github.com/elasticsearch/elasticsearch/issues/issue/447). cheers, -shay.banon ---
**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, 4:17am UTC](https://discuss.elastic.co/t/just-pushed-close-and-open-an-index/3468/2 "2017-07-06T04:17:38Z")