lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ctarg...@apache.org
Subject [lucene-solr] branch branch_8_5 updated: Ref Guide: prep upgrade notes for 8.5 release; add missing change to CHANGES.txt
Date Wed, 04 Mar 2020 22:27:24 GMT
This is an automated email from the ASF dual-hosted git repository.

ctargett pushed a commit to branch branch_8_5
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git


The following commit(s) were added to refs/heads/branch_8_5 by this push:
     new 16141e6  Ref Guide: prep upgrade notes for 8.5 release; add missing change to CHANGES.txt
16141e6 is described below

commit 16141e68de6d2857fc0c9279a784aeeea30f432b
Author: Cassandra Targett <cassandra.targett@lucidworks.com>
AuthorDate: Wed Mar 4 16:23:54 2020 -0600

    Ref Guide: prep upgrade notes for 8.5 release; add missing change to CHANGES.txt
---
 solr/CHANGES.txt                                |   7 +-
 solr/solr-ref-guide/src/solr-upgrade-notes.adoc | 120 ++++++++++++++++--------
 2 files changed, 86 insertions(+), 41 deletions(-)

diff --git a/solr/CHANGES.txt b/solr/CHANGES.txt
index bfcfb62..73b11d7 100644
--- a/solr/CHANGES.txt
+++ b/solr/CHANGES.txt
@@ -10,8 +10,8 @@ Consult the LUCENE_CHANGES.txt file for additional, low level, changes in
this r
 
 New Features
 ---------------------
- * SOLR-12490: Introducing json.queries in JSON Request API. Every property of this object
holds one or many named 
-   Query DSL queries. It's optional and doesn't impact response without explicit referencing
these queries by names 
+ * SOLR-12490: Introducing json.queries in JSON Request API. Every property of this object
holds one or many named
+   Query DSL queries. It's optional and doesn't impact response without explicit referencing
these queries by names
    (Anatolii Siuniaev via Mikhail Khludnev)
 
  * SOLR-14130: Add postlogs command line tool for indexing Solr logs (Joel Bernstein)
@@ -197,6 +197,9 @@ Other Changes
 
 * SOLR-10306: Document in Reference Guide how to disable or reduce swapping (janhoy)
 
+* SOLR-13983: Process execution is removed from SystemInfoHandler. A best-effort attempt
to
+execute `uname -a` and "`uptime`" on non-Windows platforms is no longer made. (rmuir)
+
 ==================  8.4.1 ==================
 
 Consult the LUCENE_CHANGES.txt file for additional, low level, changes in this release.
diff --git a/solr/solr-ref-guide/src/solr-upgrade-notes.adoc b/solr/solr-ref-guide/src/solr-upgrade-notes.adoc
index acf759d..29e3910 100644
--- a/solr/solr-ref-guide/src/solr-upgrade-notes.adoc
+++ b/solr/solr-ref-guide/src/solr-upgrade-notes.adoc
@@ -37,49 +37,91 @@ If you are upgrading from 7.x, see the section <<Upgrading from
7.x Releases>> b
 
 === Solr 8.5
 
-_(raw; not yet edited)_
-
-* SOLR-14026: Upgrade Jetty to 9.4.24.v20191120 and dropwizard to 4.1.2 (Erick Erickson)
-
-* SOLR-14092: BlockJoinFacetComponent is marked for deprecation and will be removed in 9.0.
-Users are encouraged to migrate to uniqueBlock() in JSON Facet API.  (Mikhail Khludnev)
-
-* SOLR-13983: Process execution is removed from SystemInfoHandler. A best-effort attempt
to
-execute "uname -a" and "uptime" on non-Windows platforms is no longer made. (rmuir)
-
-* SOLR-14095 introduces a change in the format used for the elements in the Overseer queues
and maps (see the Jira
-issue for details on the reasons for the change). This queue is used internally by the Overseer
to reliably handle
-operations, to communicate operation results between the Overseer and the coordinator node,
and by the
-REQUESTSTATUS API for displaying information about async Collection operations.
-This change won’t require you to change any client-side code you should see no differences
on the client side,
-however, it does require some care when upgrading an existing SolrCloud cluster:
-- If you are upgrading Solr with an atomic restart strategy:
-- If you don’t use async or REQUESTSTATUS operations, you should be able to restart and
not see any issues.
-- If you do use Collection API operations:
-1. pause Collection API operations
-2. cleanup queues (https://lucene.apache.org/solr/guide/8_3/collections-api.html#examples-using-deletestatus)
-if you use async operations
-3. upgrade and restart the nodes
-- If you are upgrading Solr with a rolling restart strategy:
-- If you don’t use Collection API operations, you should be able to do a rolling restart
and not see
+See the https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote85[8.5 Release Notes]
+for an overview of the main new features of Solr 8.5.
+
+When upgrading to 8.5.x users should be aware of the following major changes from 8.4.
+
+*Considerations for a SolrCloud Upgrade*
+
+Solr 8.5 introduces a change in the format used for the elements in the Overseer queues and
maps (see https://issues.apache.org/jira/browse/SOLR-14095[SOLR-14095] for technical discussion
of the change). This queue is used internally by the Overseer to reliably handle
+operations, to communicate operation results between the Overseer and the coordinator node,
and by the REQUESTSTATUS API for displaying information about async Collection operations.
+
+This change won’t require you to change any client-side code you should see no differences
on the client side.
+However, it does require some care when upgrading an existing SolrCloud cluster depending
on your upgrade strategy.
+
+If you are upgrading Solr with an atomic restart strategy:
+
+* If you don’t use async or REQUESTSTATUS operations, you should be able to restart and
not see any issues.
+* If you do use Collection API operations:
+. Pause Collection API operations.
+. Cleanup queues (See the section <<collections-api.adoc#deletestatus,DELETESTATUS>>
for examples)
+if you use async operations.
+. Upgrade and restart the nodes.
+. Resume all normal operations.
+
+If you are upgrading Solr with a rolling restart strategy:
+
+* If you don’t use Collection API operations, you should be able to do a rolling restart
and not see
 any issues.
-- If you do use Collection API operations, but you can pause their use during the restart
the easiest
+* If you do use Collection API operations, but you can pause their use during the restart
the easiest
 way is to:
-1. pause Collection API operations
-2. upgrade and restart all nodes
-3. cleanup queues (https://lucene.apache.org/solr/guide/8_3/collections-api.html#examples-using-deletestatus)
-if you use async operations
-4. Resume all normal operations
-- If you use Collection API operations and can’t pause them during the upgrade:
-1. Start 8.5 nodes with the system property: `-Dsolr.useUnsafeOverseerResponse=deserialization`.
Ensure the
-Overseer node is upgraded last
-2. Once all nodes are in 8.5 and once you don’t need to read old status anymore, restart
again removing the
-system property
-If you prefer to keep the old (but insecure) serialization strategy, you can start your nodes
using the
+. Pause Collection API operations.
+. Upgrade and restart all nodes.
+. Cleanup queues (See the section <<collections-api.adoc#deletestatus,DELETESTATUS>>
for examples)
+if you use async operations.
+. Resume all normal operations.
+
+If you use Collection API operations and can’t pause them during the upgrade:
+
+. Start 8.5 nodes with the system property: `-Dsolr.useUnsafeOverseerResponse=deserialization`.
Ensure the
+Overseer node is upgraded last.
+. Once all nodes are in 8.5 and once you don’t need to read old status anymore, restart
again removing the
+system property.
+
+If you prefer to keep the old (but insecure) serialization strategy, you can start your nodes
using the system
 property: `-Dsolr.useUnsafeOverseerResponse=true`. Keep in mind that this will be removed
in future version of Solr.
 
-* SOLR-13808: add cache=false into underneath BoolQParser's filter clause or {"bool":{"filter":..}}
to avoid caching in
-filterCache. (Mikhail Khludnev)
+*Security Manager*
+
+Solr now has the ability to run with a Java security manager enabled. To enable this, set
the property `SOLR_SECURITY_MANAGER_ENABLED=true` in `solr.in.sh` or `solr.in.cmd`. Note that
if you are using HDFS to store indexes, you cannot enable the security manager.
+
+In Solr 9.0, this will be the default.
+
+See also the section <<securing-solr.adoc#enable-security-manager,Enable Security Manager>>.
+
+*Block/Allow Specific IPs*
+
+Solr has two new parameters to allow you to restrict access to Solr using IP addresses. Use
`SOLR_IP_WHITELIST` to configure a whitelist, and `SOLR_IP_BLACKLIST` to configure a blacklist.
These properties are defined in `solr.in.sh` or `solr.in.cmd`.
+
+See also the section <<securing-solr.adoc#enable-ip-access-control,Enable IP Access
Control>>.
+
+*BlockJoin Facet Deprecation*
+
+The BlockJoinFacetComponent is marked for deprecation and will be removed in 9.0.
+Users are encouraged to migrate to `uniqueBlock()` in JSON Facet API.
+More information about this is available in the section <<json-faceting-domain-changes.adoc#block-join-domain-changes,Block
Join Domain Changes>>.
+
+*Caching with the Boolean Query Parser*
+
+By default, the <<other-parsers.adoc#boolean-query-parser,Boolean Query Parser>>
caches queries in Solr's filterCache. It's now possible to disable this with the local param
`cache=false`.
+
+*Indexing Log Files*
+
+Solr now includes a command line tool, `bin/postlogs` which will index Solr's log files into
a collection.
+This provides an easy way to use Solr or visualization tools (such as Zeppelin) to troubleshoot
problems with the system.
+
+This tool is not yet officially documented in the Reference Guide, but draft documentation
is available in a branch and can be accessed https://github.com/apache/lucene-solr/blob/visual-guide/solr/solr-ref-guide/src/logs.adoc[via
GitHub].
+
+*Highlighting*
+
+Solr's Unified Highlighter now has two parameters to help control passage sizing, `hl.fragAlignRatio`
and `hl.fragsizeIsMinimum`. See the section <<highlighting.adoc#the-unified-highlighter,The
Unified Highlighter>> for details about these new parameters.
+
+*Shared Library System Parameter*
+
+Solr's `solr.xml` file has long had support for a `sharedLib` parameter, which allows you
to define a common location for .jar files that may need to be in the path for all cores.
+
+This property can now be defined in `solr.in.sh` or `solr.in.cmd` as a system property (`-Dsolr.sharedLib=/path/to/lib`)
added to `SOLR_OPTS` (see `solr.in.sh` or `solr.in.cmd` for details).
 
 === Solr 8.4
 


Mime
View raw message