# How much state is communicated for a closed index

**URL:** https://discuss.elastic.co/t/how-much-state-is-communicated-for-a-closed-index/57922
**Category:** Elasticsearch
**Created:** [August 12, 2016, 12:43pm UTC](https://discuss.elastic.co/t/how-much-state-is-communicated-for-a-closed-index/57922 "2016-08-12T12:43:26Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![frankkoornstra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankkoornstra/32/6780_2.png) [@frankkoornstra](https://discuss.elastic.co/u/frankkoornstra)
#### Post date: [August 12, 2016, 12:43pm UTC](https://discuss.elastic.co/t/how-much-state-is-communicated-for-a-closed-index/57922/1 "2016-08-12T12:43:26Z")

</div>

in the docs for the open/close api it says

> A closed index has almost no overhead on the cluster (except for maintaining its metadata)

I was wondering what meant by _metadata_ and what is the _overhead_?

I'm asking because we had a bit too much confidence in the fact that we could put all synonyms in the mapping (turns out: too heavy, don't do it). We made a new index with all the synonyms tucked away in files but want to keep the old index for a while to see if we can trust the new one. We closed the old one but now I'm not sure if the mapping and settings of the closed index are still pumped around in the cluster because of that sentence in the docs 🙂

---

<div class="post-metadata">

### Author: ![polyfractal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/polyfractal/32/48162_2.png) [@polyfractal](https://discuss.elastic.co/u/polyfractal)
#### Post date: [August 12, 2016, 4:10pm UTC](https://discuss.elastic.co/t/how-much-state-is-communicated-for-a-closed-index/57922/2 "2016-08-12T16:10:03Z")

</div>

The metadata/overhead are essentially the information stored in the cluster state. So this includes what nodes hold each shard in the index, the settings of the index, and importantly for your case, the mappings/analysis.

What's excluded are the various in-memory datastructures that are needed to actually search the index, such as the term dictionary, posting list, ordinals, etc etc.

So in your case, the synonym list will still be persistent in the cluster state, and still impose the performance tax on the master (and network transfer between nodes). You can verify this by calling: `GET /_cluster/state`, and you'll see that the big list of synonyms is still present for that index.

When you use file-based synonyms, those values are also loaded into the cluster state. But they are only loaded when the index is opened, so if you close them they are removed from the cluster state and you'll save a bit of work on the master node.

---

<div class="post-metadata">

### Author: ![frankkoornstra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankkoornstra/32/6780_2.png) [@frankkoornstra](https://discuss.elastic.co/u/frankkoornstra)
#### Post date: [August 23, 2016, 2:19pm UTC](https://discuss.elastic.co/t/how-much-state-is-communicated-for-a-closed-index/57922/3 "2016-08-23T14:19:54Z")

</div>

Thanks for that Zachary! Sorry for the late reply, I was on vacation but it helped the developers that were solving the problem 🙂

---

<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:25pm UTC](https://discuss.elastic.co/t/how-much-state-is-communicated-for-a-closed-index/57922/4 "2017-07-05T22:25:51Z")

</div>


