You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by ct...@apache.org on 2018/06/11 13:47:47 UTC
lucene-solr:branch_7_4: SOLR-12181: Ref Guide: add link to ref'd JIRA
issue + minor punctuation fixes
Repository: lucene-solr
Updated Branches:
refs/heads/branch_7_4 bc7e6215e -> 819baf4e8
SOLR-12181: Ref Guide: add link to ref'd JIRA issue + minor punctuation fixes
Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/819baf4e
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/819baf4e
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/819baf4e
Branch: refs/heads/branch_7_4
Commit: 819baf4e8845aae392a98476006da35b797d0f9b
Parents: bc7e621
Author: Cassandra Targett <ct...@apache.org>
Authored: Mon Jun 11 08:45:50 2018 -0500
Committer: Cassandra Targett <ct...@apache.org>
Committed: Mon Jun 11 08:47:41 2018 -0500
----------------------------------------------------------------------
.../src/solrcloud-autoscaling-triggers.adoc | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/819baf4e/solr/solr-ref-guide/src/solrcloud-autoscaling-triggers.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/solrcloud-autoscaling-triggers.adoc b/solr/solr-ref-guide/src/solrcloud-autoscaling-triggers.adoc
index c91f7f0..0e77c11 100644
--- a/solr/solr-ref-guide/src/solrcloud-autoscaling-triggers.adoc
+++ b/solr/solr-ref-guide/src/solrcloud-autoscaling-triggers.adoc
@@ -117,10 +117,10 @@ this is a SPLITSHARD operation.
Similarly, when either of the lower thresholds is exceeded the trigger will generate an
event with a (configurable) requested operation to perform on two of the smallest
-shards - by default this is a MERGESHARDS operation (which is currently ignored because
-it's not yet implemented - SOLR-9407)
+shards. By default this is a MERGESHARDS operation, and is currently ignored because
+that operation is not yet implemented (see https://issues.apache.org/jira/browse/SOLR-9407[SOLR-9407]).
-Additionally, monitoring can be restricted to a list of collections - by default
+Additionally, monitoring can be restricted to a list of collections; by default
all collections are monitored.
This trigger supports the following configuration parameters (all thresholds are exclusive):
@@ -131,7 +131,8 @@ This trigger supports the following configuration parameters (all thresholds are
`aboveBytes`
`aboveDocs`:: upper threshold expressed as the number of documents. This value is compared with `SEARCHER.searcher.numDocs` metric.
-Note: due to the way Lucene indexes work a shard may exceed the `aboveBytes` threshold
++
+NOTE: Due to the way Lucene indexes work, a shard may exceed the `aboveBytes` threshold
even if the number of documents is relatively small, because replaced and deleted documents keep
occupying disk space until they are actually removed during Lucene index merging.
@@ -151,7 +152,7 @@ that exceeded thresholds and the types of violations (upper / lower bounds, byte
.Example:
This configuration specifies an index size trigger that monitors collections "test1" and "test2",
-with both bytes (1GB) and number of docs (1 mln) upper limits, and a custom `belowOp`
+with both bytes (1GB) and number of docs (1 million) upper limits, and a custom `belowOp`
operation `NONE` (which still can be monitored and acted upon by an appropriate trigger listener):
[source,json]