# Dynamic mappings are not available on the node that holds the primary yet **URL:** \ **Category:** Elasticsearch\ **Created:** [August 15, 2016, 5:31pm UTC](https://discuss.elastic.co/t/dynamic-mappings-are-not-available-on-the-node-that-holds-the-primary-yet/58046 "2016-08-15T17:31:28Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![geesu](https://avatars.discourse-cdn.com/v4/letter/g/d78d45/32.png) [@geesu](https://discuss.elastic.co/u/geesu)\ **Post date:** [August 15, 2016, 5:31pm UTC](https://discuss.elastic.co/t/dynamic-mappings-are-not-available-on-the-node-that-holds-the-primary-yet/58046/1 "2016-08-15T17:31:28Z")
We have a rails application that is using the official elasticsearch gem to connect to elasticsearch. I did a deploy which simply added one field (number) to the index (by editing the model + adding it to as\_indexed\_json) and would query by this field specifically in search. A few minutes after the deploy load spiked very hard on one of the 3 servers in our Elasticsearch cluster. And then errors starting spamming in our log: > Dynamic mappings are not available on the node that holds the primary yet. Searches started to get very, very slow, and eventually the cluster just failed entirely. We had to force restart the cluster, and remove the code that added the field/search, and things started to work perfectly fine. We did NOT do a PUT to update the mappings for the index, I was waiting for the first model index to basically do this. Any ideas/pointers would be greatly appreciated. ---
**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:27pm UTC](https://discuss.elastic.co/t/dynamic-mappings-are-not-available-on-the-node-that-holds-the-primary-yet/58046/2 "2017-07-05T22:27:40Z")