# Minimal config for testing?

**URL:** <https://discuss.elastic.co/t/minimal-config-for-testing/60257>\
**Category:** Elasticsearch\
**Created:** [September 12, 2016, 7:21am UTC](https://discuss.elastic.co/t/minimal-config-for-testing/60257 "2016-09-12T07:21:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lee\_Gee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lee_gee/32/1217_2.png) [@Lee\_Gee](https://discuss.elastic.co/u/Lee_Gee)\
**Post date:** [September 12, 2016, 7:21am UTC](https://discuss.elastic.co/t/minimal-config-for-testing/60257/1 "2016-09-12T07:21:36Z")

</div>

What is the best way to get a minimal ES configured to testing an application?

I thought this worked when I last used ES, some years ago:

```
# Disable starting multiple nodes on a single system:
node.max_local_storage_nodes: 1

```

But when I run this, the logs reads:

```
[2016-09-12 09:13:49,161][WARN][rest.suppressed] /test/posting Params: {index=test, type=posting}
RemoteTransportException[[golem-1][127.0.0.1:9300][indices:data/write/index[p]]]; nested: UnavailableShardsException[[test][2] Not enough active copies to meet write consistency of [QUORUM] (have 1, needed 3). Timeout: [1m], request: [index {[test][posting][AVcdPcIHfNWPXrF272uA], source[{"id": ...
Caused by: UnavailableShardsException[[test][2] Not enough active copies to meet write consistency of [QUORUM] (have 1, needed 3). Timeout: [1m], request: [index {[test][posting][AVcdPcIHfNWPXrF272uA], s...
...	at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryPhase.finishBecauseUnavailable(TransportReplication

```

Any help appreciated.

TIA  
Lee

---

<div class="post-metadata">

**Author:** ![javanna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javanna/32/4698_2.png) [@javanna](https://discuss.elastic.co/u/javanna)\
**Post date:** [September 12, 2016, 7:36am UTC](https://discuss.elastic.co/t/minimal-config-for-testing/60257/2 "2016-09-12T07:36:48Z")

</div>

The error you get is because you are creating an index with 2 replicas in a cluster that doesn't have enough nodes to allocate the replicas, I assume a single node cluster. When you try indexing against such a cluster you get a timeout waiting for those replicas to allocate, which they couldn't.

This behaviour didn't change though, I think you just need to change the settings for the index that you are creating if you want things to work against a single node cluster, decrease the number of replicas to 0 (or leave the default 1).

Cheers  
Luca

---

<div class="post-metadata">

**Author:** ![Lee\_Gee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lee_gee/32/1217_2.png) [@Lee\_Gee](https://discuss.elastic.co/u/Lee_Gee)\
**Post date:** [September 14, 2016, 9:41am UTC](https://discuss.elastic.co/t/minimal-config-for-testing/60257/3 "2016-09-14T09:41:30Z")

</div>

Thank you so much for your help — silly fool I am, I had a bug that meant I was loading the wrong config file, setting more shards/replicas than I thought.

---

<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:20pm UTC](https://discuss.elastic.co/t/minimal-config-for-testing/60257/4 "2017-07-05T22:20:21Z")

</div>