Hi, I've followed the documentation for zero-downtime mapping changes and it works great. http://www.elasticsearch.org/blog/changing-mapping-with-zero-downtime/
However, there is a (pretty big) race condition with this approach - while reindexing, changes may not make it to the new index. I've looked all over and haven't found a single solution to address this. The best attempt I've seen is to buffer updates, but this is tedious and still leaves a race condition (with a smaller window). My initial thoughts were to create a write alias that points to the old and new indices and use versioning. However, there is no way to write to multiple indices atomically. It seems like this issue should affect most Elasticsearch users (whether they realize it or not). Does anyone have a good solution to this? Thanks, Andrew -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f633b7d6-67a6-464f-b0ad-fe478ae85cc6%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
