lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [1/4] lucene-solr:branch_7_6: SOLR-12927: Add upgrade notes for Solr 7.6
Date Tue, 13 Nov 2018 14:22:15 GMT
Repository: lucene-solr
Updated Branches:
  refs/heads/branch_7_6 5cee6e467 -> 1b29b57d7

SOLR-12927: Add upgrade notes for Solr 7.6


Branch: refs/heads/branch_7_6
Commit: a03fe7fdbb29885e60790fedaed193ad2e114014
Parents: 5cee6e4
Author: Cassandra Targett <>
Authored: Mon Nov 12 08:55:05 2018 -0600
Committer: Cassandra Targett <>
Committed: Tue Nov 13 08:19:10 2018 -0600

 solr/solr-ref-guide/src/solr-upgrade-notes.adoc | 57 ++++++++++++++++++++
 1 file changed, 57 insertions(+)
diff --git a/solr/solr-ref-guide/src/solr-upgrade-notes.adoc b/solr/solr-ref-guide/src/solr-upgrade-notes.adoc
index 40892b2..516598d 100644
--- a/solr/solr-ref-guide/src/solr-upgrade-notes.adoc
+++ b/solr/solr-ref-guide/src/solr-upgrade-notes.adoc
@@ -27,6 +27,63 @@ Detailed steps for upgrading a Solr cluster are in the section <<upgrading-a-sol
 == Upgrading to 7.x Releases
+=== Solr 7.6
+See the[7.6 Release Notes] for an overview of
the main new features in Solr 7.6.
+When upgrading to Solr 7.6, users should be aware of the following major changes from v7.5:
+* The JSON parameter to set cluster-wide default cluster properties with the <<collections-api.adoc#clusterprop,CLUSTERPROP>>
command has changed.
+The old syntax nested the defaults into a property named `clusterDefaults`. The new syntax
uses only `defaults`. The command to use is still `set-obj-property`.
+An example of the new syntax is:
+  "set-obj-property": {
+    "defaults" : {
+      "collection": {
+        "numShards": 2,
+        "nrtReplicas": 1,
+        "tlogReplicas": 1,
+        "pullReplicas": 1
+      }
+    }
+  }
+The old syntax will be supported until at least Solr 9, but users are advised to begin using
the new syntax as soon as possible.
+* The parameter `min_rf` has been deprecated and no longer needs to be provided in order
to see the achieved replication factor. This information will now always be returned to the
client with the response.
+* An autoscaling policy is now used as the default strategy for selecting nodes on which
new replicas or replicas of new collections are created.
+A default policy is now in place for all users, which will sort nodes by the number of cores
and available freedisk, which means by default a node with the fewest number of cores already
on it and the highest available freedisk will be selected for new core creation.
+* The change described above has two additional impacts on the `maxShardsPerNode` parameter:
+. 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.
+* Lucene has introduced the `ByteBuffersDirectory` as a replacement for the `RAMDirectoryFactory`,
which will be removed in Solr 9.
+While most users are still encouraged to use the `NRTCachingDirectoryFactory`, which allows
Lucene to select the best directory factory to use, if you have explicitly configured Solr
to use the `RAMDirectoryFactory`, you are encouraged to switch to the new implementation as
soon as possible before Solr 9 is released.
+For more information about the new directory factory, see the Jira issue[LUCENE-8438].
+For more information about the directory factory configuration in Solr, see the section <<datadir-and-directoryfactory-in-solrconfig.adoc#datadir-and-directoryfactory-in-solrconfig,DataDir
and DirectoryFactory in SolrConfig>>.
 === Solr 7.5
 See the[7.5 Release Notes] for an overview of
the main new features in Solr 7.5.

View raw message