Apache
/
lucene
mirror of https://github.com/apache/lucene.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

SOLR-11277: Documentation for maxSize based auto hard commit

This commit is contained in:
Anshum Gupta 2018-06-18 09:56:43 -07:00
parent 90145d0112
commit 6222c46201
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
solr/solr-ref-guide/src/updatehandlers-in-solrconfig.adoc
View File

@ -47,10 +47,13 @@ The number of updates that have occurred since the last commit.
`maxTime`:: `maxTime`::
The number of milliseconds since the oldest uncommitted update. The number of milliseconds since the oldest uncommitted update.
`maxSize`::
The maxSize of the transaction log, after which a hard commit is triggered. This is useful when the size of documents is unknown and the intention is to restric the size of the tlog to reasonable size.
`openSearcher`:: `openSearcher`::
Whether to open a new searcher when performing a commit. If this is `false`, the commit will flush recent index changes to stable storage, but does not cause a new searcher to be opened to make those changes visible. The default is `true`. Whether to open a new searcher when performing a commit. If this is `false`, the commit will flush recent index changes to stable storage, but does not cause a new searcher to be opened to make those changes visible. The default is `true`.
If either of the `maxDocs` or `maxTime` limits are reached, Solr automatically performs a commit operation. If the `autoCommit` tag is missing, then only explicit commits will update the index. The decision whether to use auto-commit or not depends on the needs of your application. If any of the `maxDocs`, `maxTime`, or `maxSize` limits are reached, Solr automatically performs a commit operation. If the `autoCommit` tag is missing, then only explicit commits will update the index. The decision whether to use auto-commit or not depends on the needs of your application.
Determining the best auto-commit settings is a tradeoff between performance and accuracy. Settings that cause frequent updates will improve the accuracy of searches because new content will be searchable more quickly, but performance may suffer because of the frequent updates. Less frequent updates may improve performance but it will take longer for updates to show up in queries. Determining the best auto-commit settings is a tradeoff between performance and accuracy. Settings that cause frequent updates will improve the accuracy of searches because new content will be searchable more quickly, but performance may suffer because of the frequent updates. Less frequent updates may improve performance but it will take longer for updates to show up in queries.
@ -59,6 +62,7 @@ Determining the best auto-commit settings is a tradeoff between performance and
<autoCommit> <autoCommit>
<maxDocs>10000</maxDocs> <maxDocs>10000</maxDocs>
<maxTime>30000</maxTime> <maxTime>30000</maxTime>
<maxSize>512m</maxSize>
<openSearcher>false</openSearcher> <openSearcher>false</openSearcher>
</autoCommit> </autoCommit>
---- ----