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
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.
On Thu, Nov 4, 2010 at 9:59 PM, John Chang email@example.com wrote:
We add field mappings to our document types upon new index creation and it
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:
[indices.cluster] - [Scrambler] [index0] failed to add mapping [mail],
[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:
Sent from the ElasticSearch Users mailing list archive at Nabble.com.