# New indices does not pick up changes to synonym-files, hunspell etc

**URL:** <https://discuss.elastic.co/t/new-indices-does-not-pick-up-changes-to-synonym-files-hunspell-etc/67837>\
**Category:** Elasticsearch\
**Created:** [December 2, 2016, 9:22am UTC](https://discuss.elastic.co/t/new-indices-does-not-pick-up-changes-to-synonym-files-hunspell-etc/67837 "2016-12-02T09:22:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mekanix](https://avatars.discourse-cdn.com/v4/letter/m/9de0a6/32.png) [@mekanix](https://discuss.elastic.co/u/mekanix)\
**Post date:** [December 2, 2016, 9:22am UTC](https://discuss.elastic.co/t/new-indices-does-not-pick-up-changes-to-synonym-files-hunspell-etc/67837/1 "2016-12-02T09:22:17Z")

</div>

Hi

We have this weird thing.

We have these hunspell and synonym files in config/ that works fine in our analyzers.

But when we make changes to those, they are not used in any _new_ indices we create - they are still using the old ones.

So it appears that Elasticsearch is caching the files - even for new indices?

It wasn't until we restarted elasticsearch (out of desperation 🙂 ) that the changes were picked up.

Is this the expected behaviour? Or is there a proper way to tell elasticsearch to use the new files (we can't seem to find it in the documentation).

There are some blips about turning _existing_ indices off and on again to pick up new files - but that wouldn't apply to new indices?

- Bjarne

---

<div class="post-metadata">

**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\
**Post date:** [December 2, 2016, 12:48pm UTC](https://discuss.elastic.co/t/new-indices-does-not-pick-up-changes-to-synonym-files-hunspell-etc/67837/2 "2016-12-02T12:48:00Z")

</div>

sounds weird indeed and looks like a bug to me (at first glance)!

Looking at the code, it also seems that this is fixed in ES v5.0.0 by [https://github.com/elastic/elasticsearch/issues/19827](https://github.com/elastic/elasticsearch/issues/19827)

/ping @nik9000

---

<div class="post-metadata">

**Author:** ![mekanix](https://avatars.discourse-cdn.com/v4/letter/m/9de0a6/32.png) [@mekanix](https://discuss.elastic.co/u/mekanix)\
**Post date:** [December 14, 2016, 2:06pm UTC](https://discuss.elastic.co/t/new-indices-does-not-pick-up-changes-to-synonym-files-hunspell-etc/67837/3 "2016-12-14T14:06:06Z")

</div>

We did another round of updates, and this time the changes was picked up without us needing to restart ES.

So maybe just a fluke? Or could it be that last time we did do frequent succesive updates (we were testing) and ES doesn't reload that often?

---

<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:** [January 11, 2017, 2:06pm UTC](https://discuss.elastic.co/t/new-indices-does-not-pick-up-changes-to-synonym-files-hunspell-etc/67837/4 "2017-01-11T14:06:18Z")

</div>

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