# Unexpected (and failed) attempts to add field analyzer mappings **URL:** \ **Category:** Elasticsearch\ **Created:** [November 4, 2010, 7:59pm UTC](https://discuss.elastic.co/t/unexpected-and-failed-attempts-to-add-field-analyzer-mappings/3520 "2010-11-04T19:59:06Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![John\_Chang](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@John\_Chang](https://discuss.elastic.co/u/John_Chang)\ **Post date:** [November 4, 2010, 7:59pm UTC](https://discuss.elastic.co/t/unexpected-and-failed-attempts-to-add-field-analyzer-mappings/3520/1 "2010-11-04T19:59:06Z")
We add field mappings to our document types upon new index creation and it works well. However, we see odd attempts to re-add the analyzer mappings at the startup time of our services that instantiate no-data elastic search nodes. There is nothing in our startup sequence that send off these mappings that we can see. It just looks like it is re-adding the mappings (or at least some of them), and it fails. For example from our logs at startup time: 19:55:53,388 WARN [elasticsearch[Scrambler]clusterService#updateTask-pool-7-thread-1] [indices.cluster] - [Scrambler] [index0] failed to add mapping [mail], source [org.elasticsearch.common.compress.CompressedString@bb75f1ce] org.elasticsearch.index.mapper.MapperParsingException: Analyzer [kihaSnowball] not found for field [to] We've started seeing this after startup time as well. Again, all is working fine, and when we check the mappings, they are happy. We just see these concerning errors in the logs. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 4, 2010, 9:55pm UTC](https://discuss.elastic.co/t/unexpected-and-failed-attempts-to-add-field-analyzer-mappings/3520/2 "2010-11-04T21:55:26Z")
I am guessing this is because the analyzer is not defined in the non data nodes settings as well. In 0.12, the high level indexes were created on all nodes (each high level index can have zero or more shards allocated), and some data is associated with it, for example, parsed mappings, analyzers and so on. As part of the effort to improve cases where many indices are created, in master (0.13) there as been quite a big refactoring, causing those high level index constructs to be created only if a shard is allocated on that node. Of course, for non data nodes, this will never happen, so you won't need to define these analyzers on the node itself. -shay.banon On Thu, Nov 4, 2010 at 9:59 PM, John Chang [jchangkihtest2@gmail.com](mailto:jchangkihtest2@gmail.com) wrote: > We add field mappings to our document types upon new index creation and it > works well. > > However, we see odd attempts to re-add the analyzer mappings at the startup > time of our services that instantiate no-data Elasticsearch nodes. There > is nothing in our startup sequence that send off these mappings that we can > see. It just looks like it is re-adding the mappings (or at least some of > them), and it fails. For example from our logs at startup time: > > 19:55:53,388 WARN > [elasticsearch[Scrambler]clusterService#updateTask-pool-7-thread-1] > [indices.cluster] - [Scrambler] [index0] failed to add mapping [mail], > source [org.elasticsearch.common.compress.CompressedString@bb75f1ce] > org.elasticsearch.index.mapper.MapperParsingException: Analyzer > [kihaSnowball] not found for field [to] > > We've started seeing this after startup time as well. > > Again, all is working fine, and when we check the mappings, they are happy. > We just see these concerning errors in the logs. > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Unexpected-and-failed-attempts-to-add-field-analyzer-mappings-tp1844246p1844246.html](http://elasticsearch-users.115913.n3.nabble.com/Unexpected-and-failed-attempts-to-add-field-analyzer-mappings-tp1844246p1844246.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![James\_Cook](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@James\_Cook](https://discuss.elastic.co/u/James_Cook)\ **Post date:** [November 5, 2010, 1:03am UTC](https://discuss.elastic.co/t/unexpected-and-failed-attempts-to-add-field-analyzer-mappings/3520/3 "2010-11-05T01:03:16Z")
I hope the book will be released at the same time ES 1.0! 😃 On Thu, Nov 4, 2010 at 5:55 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > I am guessing this is because the analyzer is not defined in the non data > nodes settings as well. In 0.12, the high level indexes were created on all > nodes (each high level index can have zero or more shards allocated), and > some data is associated with it, for example, parsed mappings, analyzers and > so on. > > As part of the effort to improve cases where many indices are created, in > master (0.13) there as been quite a big refactoring, causing those high > level index constructs to be created only if a shard is allocated on that > node. Of course, for non data nodes, this will never happen, so you won't > need to define these analyzers on the node itself. > > -shay.banon > > On Thu, Nov 4, 2010 at 9:59 PM, John Chang [jchangkihtest2@gmail.com](mailto:jchangkihtest2@gmail.com)wrote: > > > We add field mappings to our document types upon new index creation and it > > works well. > > > > However, we see odd attempts to re-add the analyzer mappings at the > > startup > > time of our services that instantiate no-data Elasticsearch nodes. There > > is nothing in our startup sequence that send off these mappings that we > > can > > see. It just looks like it is re-adding the mappings (or at least some of > > them), and it fails. For example from our logs at startup time: > > > > 19:55:53,388 WARN > > [elasticsearch[Scrambler]clusterService#updateTask-pool-7-thread-1] > > [indices.cluster] - [Scrambler] [index0] failed to add mapping [mail], > > source [org.elasticsearch.common.compress.CompressedString@bb75f1ce] > > org.elasticsearch.index.mapper.MapperParsingException: Analyzer > > [kihaSnowball] not found for field [to] > > > > We've started seeing this after startup time as well. > > > > Again, all is working fine, and when we check the mappings, they are > > happy. > > We just see these concerning errors in the logs. > > > > -- > > View this message in context: > > [http://elasticsearch-users.115913.n3.nabble.com/Unexpected-and-failed-attempts-to-add-field-analyzer-mappings-tp1844246p1844246.html](http://elasticsearch-users.115913.n3.nabble.com/Unexpected-and-failed-attempts-to-add-field-analyzer-mappings-tp1844246p1844246.html) > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:17am UTC](https://discuss.elastic.co/t/unexpected-and-failed-attempts-to-add-field-analyzer-mappings/3520/4 "2017-07-06T04:17:06Z")