elasticsearch/elasticsearch — Issue #1656: Robustness issues with mapping type conflicts (0.18.7)
Author: Alex-Ikanow
Created: 2012-02-01 14:33:40+00:00
State: open

This occurs 100% on my operational cluster, but my attempt to recreate via a simple GIST (https://gist.github.com/1717268) fails.

I was indexing a large number of documents into several different indexes, with an identical mapping. The documents can also contain "unmapped" fields containing arrays of "user-specified" objects.

In this case, in the first document with such an unmapped field, the object contained a field with a null that my calling program had incorrectly turned into {}

(Somewhat less simplified example of documents: https://gist.github.com/1717326)

When the next document (with a correct string field) was indexed, the calling thread went into a tight loop forever (ie the index hung, 1 CPU went to 100%). Trying multiple times, more CPUs went to 100%.

When I closed down the offending node, one of the other nodes would thrash, until I had closed all the nodes down and restarted them 1-by-1.

Assuming the above is no use (!), when I get some more time I'll try to make my reproduction more and more like my real world case until it fails. (Be a couple of weeks, will leave this as a placeholder until then?)