[lucene] 10/15: SOLR-11277: Documentation for maxSize based auto hard commit

[dw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

dweiss pushed a commit to branch branch_7_4
in repository https://gitbox.apache.org/repos/asf/lucene.git

commit f3a984e320ccee1006058d4ef924c4dbd359dbaf
Author: Anshum Gupta <an...@apache.org>
AuthorDate: Mon Jun 18 09:56:43 2018 -0700

    SOLR-11277: Documentation for maxSize based auto hard commit
---
 solr/solr-ref-guide/src/updatehandlers-in-solrconfig.adoc | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/solr/solr-ref-guide/src/updatehandlers-in-solrconfig.adoc b/solr/solr-ref-guide/src/updatehandlers-in-solrconfig.adoc
index cd60315..bad06d9 100644
--- a/solr/solr-ref-guide/src/updatehandlers-in-solrconfig.adoc
+++ b/solr/solr-ref-guide/src/updatehandlers-in-solrconfig.adoc
@@ -47,10 +47,13 @@ The number of updates that have occurred since the last commit.
 `maxTime`::
 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`::
 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.
 
@@ -59,6 +62,7 @@ Determining the best auto-commit settings is a tradeoff between performance and
 <autoCommit>
   <maxDocs>10000</maxDocs>
   <maxTime>30000</maxTime>
+  <maxSize>512m</maxSize>
   <openSearcher>false</openSearcher>
 </autoCommit>
 ----