Elasticsearch performance when dynamic mapping vs strict/false

(Sep) #1


I couldn't find any material regarding benchmarking of Elasticsearch with dynamic mapping vs strict/false. Has anybody experienced performance issues when using dynamic mapping?

From what I understand when dynamic mapping is allowed, indexing a new document that has a new field will cause all documents in the shard to be re-indexed so they all have the new field. And depending on the size of documents that will cause performance issues. Is that correct?


(Christian Dahlqvist) #2

No, no documents will be reindexed but the cluster state will need to be updated and distributed with the new mapping. If you have large mappings an/or lots of indices/shards this can be slow and affect indexing performance. Generally it will however not have much impact though.

(Sep) #3

Cool. Thanks for the response.

(system) closed #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.