elasticsearch/elasticsearch — Issue #1619: concurrent inserts cause an index to be deleted
Author: abdollar
Created: 2012-01-18 02:55:44+00:00
State: open

I have an application that performs concurrent inserts on an elasticsearch index and is using 4 cpus on a cluster with 5 nodes using 0.18.5 - a single node has 16 cores and inserts are being performed on the node with the elasticsearch instance.

At a certain point in time (and its not that predictable) I see remove_mapping in the logs and a new index is being referenced when using count.

If I force/bind the application that performs the inserts to one cpu the problem goes away ; as in the index does not get rebuilt and index counts don't get reset and I don't see remove_mapping in the logs