From 7eb730f6e036f4d89b00e60f01a10c2c64baa44b Mon Sep 17 00:00:00 2001 From: Christine Poerschke Date: Thu, 11 Jul 2019 09:09:17 +0100 Subject: [PATCH] Fix couple of solr-ref-guide typos. --- solr/solr-ref-guide/src/major-changes-in-solr-8.adoc | 2 +- solr/solr-ref-guide/src/solr-system-requirements.adoc | 2 +- solr/solr-ref-guide/src/taking-solr-to-production.adoc | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc b/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc index ac19109531e..9b0a3233438 100644 --- a/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc +++ b/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc @@ -337,7 +337,7 @@ A default policy is now in place for all users, which will sort nodes by the num . It removes the restriction against using `maxShardsPerNode` when an autoscaling policy is in place. This parameter can now always be set when creating a collection. . It removes the default setting of `maxShardsPerNode=1` when an autoscaling policy is in place. It will be set correctly (if required) regardless of whether an autoscaling policy is in place or not. + -The default value of `maxShardsPerNode` is still `1`. It can be set to `-1` if the old behavior of unlimited `maxSharedsPerNode` is desired. +The default value of `maxShardsPerNode` is still `1`. It can be set to `-1` if the old behavior of unlimited `maxShardsPerNode` is desired. *DirectoryFactory* diff --git a/solr/solr-ref-guide/src/solr-system-requirements.adoc b/solr/solr-ref-guide/src/solr-system-requirements.adoc index 95c5d4146bd..6a4bdd48cca 100644 --- a/solr/solr-ref-guide/src/solr-system-requirements.adoc +++ b/solr/solr-ref-guide/src/solr-system-requirements.adoc @@ -43,7 +43,7 @@ Some versions of Java VM have bugs that may impact your implementation. To be su === Sources for Java -Java is available from a number of providers. Lucene and Solr regularly test with https://jdk.java.net/[OpenJDK] nad Oracle versions of Java. Some are free, others have a cost, some provide security patches and support, others do not. We recommend you read the article https://medium.com/@javachampions/java-is-still-free-2-0-0-6b9aa8d6d244[Java is still free by Java Champions] to help you decide. +Java is available from a number of providers. Lucene and Solr regularly test with https://jdk.java.net/[OpenJDK] and Oracle versions of Java. Some are free, others have a cost, some provide security patches and support, others do not. We recommend you read the article https://medium.com/@javachampions/java-is-still-free-2-0-0-6b9aa8d6d244[Java is still free by Java Champions] to help you decide. The Lucene project does not endorse any particular provider of Java. diff --git a/solr/solr-ref-guide/src/taking-solr-to-production.adoc b/solr/solr-ref-guide/src/taking-solr-to-production.adoc index 873d4e29965..9e3595d492c 100644 --- a/solr/solr-ref-guide/src/taking-solr-to-production.adoc +++ b/solr/solr-ref-guide/src/taking-solr-to-production.adoc @@ -175,7 +175,7 @@ The auto-detected value is exposed by the <> so that values appropriate to your hardware are used. -Alternatively, the boolean system property `lucene.cms.override_spins` can be set in the `SOLR_OPTS` variable in the include file to override the auto-detected value. Similarily, the system property `lucene.cms.override_core_count` can be set to the number of CPU cores to override the auto-detected processor count. +Alternatively, the boolean system property `lucene.cms.override_spins` can be set in the `SOLR_OPTS` variable in the include file to override the auto-detected value. Similarly, the system property `lucene.cms.override_core_count` can be set to the number of CPU cores to override the auto-detected processor count. === Memory and GC Settings @@ -187,7 +187,7 @@ SOLR_JAVA_MEM="-Xms10g -Xmx10g" ---- Also, the <> comes with a set of pre-configured Garbage First Garbage Collection settings that have shown to work well with Solr for a number of different workloads. -However, these settings may not work well for your specific use of Solr. Consequently, you may need to change the GC settings, which should also be done with the `GC_TUNE` variable in the `/etc/default/solr.in.sh` include file. For more information about garbage collection settings refer to folowing articles: +However, these settings may not work well for your specific use of Solr. Consequently, you may need to change the GC settings, which should also be done with the `GC_TUNE` variable in the `/etc/default/solr.in.sh` include file. For more information about garbage collection settings refer to following articles: 1. https://wiki.apache.org/solr/ShawnHeisey 2. https://www.oracle.com/technetwork/articles/java/g1gc-1984535.html You can also refer to <> for tuning your memory and garbage collection settings.