Do not optimize Solr index after each add/delete #135
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
From https://wiki.apache.org/solr/UpdateXmlMessages : An optimize is like a hard commit except that it forces all of the index segments to be merged into a single segment first. Depending on the use cases, this operation should be performed infrequently (like nightly), if at all, since it is very expensive and involves reading and re-writing the entire index. Segments are normally merged over time anyway (as determined by the merge policy), and optimize just forces these merges to occur immediately. This patch removes all calls to optimize() except where it makes sense to have them (indexAll, deleteAll, hookUninstall)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From https://wiki.apache.org/solr/UpdateXmlMessages :
An optimize is like a hard commit except that it forces all of the index
segments to be merged into a single segment first. Depending on the use cases,
this operation should be performed infrequently (like nightly), if at all,
since it is very expensive and involves reading and re-writing the entire
index. Segments are normally merged over time anyway (as determined by the
merge policy), and optimize just forces these merges to occur immediately.
This patch removes all calls to optimize() except where it makes sense to have
them (indexAll, deleteAll, hookUninstall)