# 2.2.0 ESIntegTestCase: ensureYellow() results in "timed out waiting for yellow" - "unavailable\_shards\_exception" **URL:** \ **Category:** Elasticsearch\ **Created:** [March 8, 2016, 9:53pm UTC](https://discuss.elastic.co/t/2-2-0-esintegtestcase-ensureyellow-results-in-timed-out-waiting-for-yellow-unavailable-shards-exception/43835 "2016-03-08T21:53:17Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Olafur\_Gauti\_Gudmund](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/olafur_gauti_gudmund/32/2694_2.png) [@Olafur\_Gauti\_Gudmund](https://discuss.elastic.co/u/Olafur_Gauti_Gudmund)\ **Post date:** [March 8, 2016, 9:53pm UTC](https://discuss.elastic.co/t/2-2-0-esintegtestcase-ensureyellow-results-in-timed-out-waiting-for-yellow-unavailable-shards-exception/43835/1 "2016-03-08T21:53:17Z")
I am in the process of rewriting our integration tests to work with Elasticsearch 2.2.0. I have an abstract test case class which extends `org.elasticsearch.test.ESIntegTestCase`: ``` @ESIntegTestCase.ClusterScope(scope = ESIntegTestCase.Scope.SUITE, numDataNodes = 1) @ThreadLeakScope(ThreadLeakScope.Scope.NONE) public abstract class AbstractApplicationTest extends ESIntegTestCase { ... @Override protected Settings nodeSettings(int nodeOrdinal) { return Settings.settingsBuilder() .put(super.nodeSettings(nodeOrdinal)) .put(IndexMetaData.SETTING_NUMBER_OF_SHARDS, 1) .put(IndexMetaData.SETTING_NUMBER_OF_REPLICAS, 1) .put(Node.HTTP_ENABLED, true) .put("script.groovy.sandbox.enabled", true) .put("script.engine.groovy.inline.search", true) .put("script.engine.groovy.inline.update", "true") .put("script.inline", true) .put("script.update", true) .put("script.indexed", true) .put("script.default_lang", "groovy") .build(); } @Override protected Collection> nodePlugins() { return pluginList(GroovyPlugin.class, DeleteByQueryPlugin.class, AnalysisICUPlugin.class); } @Before public void setUpElastic() throws Exception { // add the index and the mappings prepareCreate("bokun") .setSettings(Settings.builder().loadFromSource(loadFromClasspath("indices/settings.json"))) .addMapping(AccommodationSearchIndex.INDEX_ACCOMMODATION_TYPE, loadFromClasspath("indices/accommodation.json")) .addMapping(AccommodationSearchIndex.INDEX_ROOM_TYPE, loadFromClasspath("indices/room.json")) ... .execute().actionGet(); ensureYellow(); } ... } ``` My test case class extends this abstract class. It has 6 tests, and constantly 3-4 of them fail with the "timed out waiting for yellow" message during the call `ensureYellow()` above. The test case scope is `ESIntegTestCase.Scope.SUITE`, which means that a cluster will be created for each SUITE rather than test, and then I am creating the index and adding mappings before each test. I assume that after each test the index is deleted, as this page states: [Integration tests | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/integration-tests.html) > By default the tests are run with unique cluster per test suite. Of course all indices and templates are deleted between each test. Does anyone know what I am doing wrong here? P.S. I am using SBT to run my tests. ---
**Author:** ![Olafur\_Gauti\_Gudmund](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/olafur_gauti_gudmund/32/2694_2.png) [@Olafur\_Gauti\_Gudmund](https://discuss.elastic.co/u/Olafur_Gauti_Gudmund)\ **Post date:** [March 9, 2016, 10:59am UTC](https://discuss.elastic.co/t/2-2-0-esintegtestcase-ensureyellow-results-in-timed-out-waiting-for-yellow-unavailable-shards-exception/43835/2 "2016-03-09T10:59:25Z")
If I comment out the `ensureYellow()` call, then I am getting `"unavailable_shards_exception"` from Elasticsearch when executing index requests: ``` { "took": 60001, "errors": true, "items": [{ "index": { "_index": "bokun", "_type": "activity_availability", "_id": "20_20160309", "status": 503, "error": { "type": "unavailable_shards_exception", "reason": "[bokun][2] primary shard is not active Timeout: [1m], request: [shard bulk {[bokun][2]}]" } } }, { "index": { "_index": "bokun", "_type": "activity_availability", "_id": "20_20160310", "status": 503, "error": { "type": "unavailable_shards_exception", "reason": "[bokun][1] primary shard is not active Timeout: [1m], request: [shard bulk {[bokun][1]}]" } } }, ... { "index": { "_index": "bokun", "_type": "activity_availability", "_id": "20_20160322", "status": 503, "error": { "type": "unavailable_shards_exception", "reason": "[bokun][0] primary shard is not active Timeout: [1m], request: [shard bulk {[bokun][0]}]" } } }, { "index": { "_index": "bokun", "_type": "activity", "_id": "12", "status": 503, "error": { "type": "unavailable_shards_exception", "reason": "[bokun][2] primary shard is not active Timeout: [1m], request: [shard bulk {[bokun][2]}]" } } }] } ``` ---
**Author:** ![Olafur\_Gauti\_Gudmund](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/olafur_gauti_gudmund/32/2694_2.png) [@Olafur\_Gauti\_Gudmund](https://discuss.elastic.co/u/Olafur_Gauti_Gudmund)\ **Post date:** [March 9, 2016, 1:09pm UTC](https://discuss.elastic.co/t/2-2-0-esintegtestcase-ensureyellow-results-in-timed-out-waiting-for-yellow-unavailable-shards-exception/43835/3 "2016-03-09T13:09:59Z")
I've solved this. Elasticsearch logging was not showing up in my console. When I enabled that, I could see the actual cause of the problem: ``` ensureYellow timed out, cluster state: version: 8 state uuid: twZ91SH7QIytVTrQuixDbg from_diff: false meta data version: 3 nodes: {node_s0}{H_1t-4MwSKueM5vXRw_P4A}{local}{local[1]}{mode=local}, local, master routing_table (version 6): -- index [bokun] ----shard_id [bokun][0] --------[bokun][0], node[null], [P], v[3], s[UNASSIGNED], unassigned_info[[reason=ALLOCATION_FAILED], at[2016-03-09T13:07:48.812Z], details[failed to update mappings, failure IllegalArgumentException[Mapper for [translations.excerpt] conflicts with existing mapping in other types: [mapper [translations.excerpt] has different [store] values]]]] ``` ---
**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, 11:09pm UTC](https://discuss.elastic.co/t/2-2-0-esintegtestcase-ensureyellow-results-in-timed-out-waiting-for-yellow-unavailable-shards-exception/43835/4 "2017-07-05T23:09:53Z")