Optimize dynamic mapping updates on master by processing latest one per index/node #4373
Assignees
Labels
Comments
kimchy
added a commit
that referenced
this issue
Dec 7, 2013
…er index/node Instead of processing all the bulk of update mappings we have per index/node, we can only update the last ordered one out of those (cause they are incremented on the node/index level). This will improve the processing time of an index that have large updates of mappings. closes #4373
ghost
assigned
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
…er index/node Instead of processing all the bulk of update mappings we have per index/node, we can only update the last ordered one out of those (cause they are incremented on the node/index level). This will improve the processing time of an index that have large updates of mappings. closes elastic#4373
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Instead of processing all the bulk of update mappings we have per index/node, we can only update the last ordered one out of those (cause they are incremented on the node/index level). This will improve the processing time of an index that have large updates of mappings.
The text was updated successfully, but these errors were encountered: