# Is there any best practices for maintaining index in production?

**URL:** <https://discuss.elastic.co/t/is-there-any-best-practices-for-maintaining-index-in-production/179658>\
**Category:** Elasticsearch\
**Created:** [May 5, 2019, 9:00am UTC](https://discuss.elastic.co/t/is-there-any-best-practices-for-maintaining-index-in-production/179658 "2019-05-05T09:00:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Morriaty](https://avatars.discourse-cdn.com/v4/letter/m/8e8cbc/32.png) [@Morriaty](https://discuss.elastic.co/u/Morriaty)\
**Post date:** [May 5, 2019, 9:00am UTC](https://discuss.elastic.co/t/is-there-any-best-practices-for-maintaining-index-in-production/179658/1 "2019-05-05T09:00:06Z")

</div>

This official blog [Changing Mapping with Zero Downtime](https://www.elastic.co/cn/blog/changing-mapping-with-zero-downtime) helps a lot, but things get much more complicated in real world.

There are still some problems left:

1. what if write operations go in the meanwhile when switching alias?
2. what if terms (new words, stop words) change frequently with big size index. Say an index of 1million docs, some new words affects some hundreds docs but change frequently. It's not worthy to do full size reindex everytime.

And some other problems I can't recall at once.

Would you please recommend some blogs major in production search engine so that I can follow?

Thanks for help!

---

<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:** [June 2, 2019, 9:00am UTC](https://discuss.elastic.co/t/is-there-any-best-practices-for-maintaining-index-in-production/179658/2 "2019-06-02T09:00:08Z")

</div>

Closed on June 2, 2019, 9:00am UTC

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