# Testing: new index vs. new cluster

**URL:** <https://discuss.elastic.co/t/testing-new-index-vs-new-cluster/126425>\
**Category:** Elasticsearch\
**Created:** [April 2, 2018, 12:43pm UTC](https://discuss.elastic.co/t/testing-new-index-vs-new-cluster/126425 "2018-04-02T12:43:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pisush](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pisush/32/25568_2.png) [@Pisush](https://discuss.elastic.co/u/Pisush)\
**Post date:** [April 2, 2018, 12:43pm UTC](https://discuss.elastic.co/t/testing-new-index-vs-new-cluster/126425/1 "2018-04-02T12:43:30Z")

</div>

Reading a bit about testing Elastic, 2 options are possible:  
Dedicating an index in the cluster used in production and setting up an in memory cluster.

The first option is good mainly because it allows testing IRL behaviour;  
the latter is good mainly because you don't mess with things in production for testing purposes.

There is also the option of setting up a remote cluster for testing, but have yet to see it.

I'd love to hear what is the practice you are using - first/second/both/third?  
What are your main pros and cons?

---

<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:** [April 30, 2018, 12:44pm UTC](https://discuss.elastic.co/t/testing-new-index-vs-new-cluster/126425/2 "2018-04-30T12:44:24Z")

</div>

Closed on April 30, 2018, 12:44pm UTC

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