# Is there some sort of preproduction staging mechanism (reindexing takes quite some time)

**URL:** <https://discuss.elastic.co/t/is-there-some-sort-of-preproduction-staging-mechanism-reindexing-takes-quite-some-time/192915>\
**Category:** Elasticsearch\
**Created:** [July 30, 2019, 2:05pm UTC](https://discuss.elastic.co/t/is-there-some-sort-of-preproduction-staging-mechanism-reindexing-takes-quite-some-time/192915 "2019-07-30T14:05:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tom2](https://avatars.discourse-cdn.com/v4/letter/t/97f17d/32.png) [@tom2](https://discuss.elastic.co/u/tom2)\
**Post date:** [July 30, 2019, 2:05pm UTC](https://discuss.elastic.co/t/is-there-some-sort-of-preproduction-staging-mechanism-reindexing-takes-quite-some-time/192915/1 "2019-07-30T14:05:24Z")

</div>

Hi there,

I'm currently evaluating Elasticsearch for our project. In this project we want to completely reindex our database from time to time, which will probably take a few hours up to a couple of days.  
This must not affect the database in production, as users are working with the system 24/7.

And here is my question:

- Is there a best practice around how to achieve this?

Any hints or keywords to search for highly appreciated.

Kind regards  
Tom

P.S.: My current toughts on this:

- Should we index the data into another cluster, node or index?
- Can we replicate it into our live system?
- Should we write data with some sort of notYetVisible boolean?

---

<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:** [August 27, 2019, 2:05pm UTC](https://discuss.elastic.co/t/is-there-some-sort-of-preproduction-staging-mechanism-reindexing-takes-quite-some-time/192915/2 "2019-08-27T14:05:24Z")

</div>

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