lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Confluence)" <conflue...@apache.org>
Subject [CONF] Apache Solr Reference Guide > Upgrading Solr
Date Thu, 25 Jul 2013 17:55:00 GMT
Space: Apache Solr Reference Guide (https://cwiki.apache.org/confluence/display/solr)
Page: Upgrading Solr (https://cwiki.apache.org/confluence/display/solr/Upgrading+Solr)

Change Comment:
---------------------------------------------------------------------
rename as top level upgrade page

Edited by Hoss Man:
---------------------------------------------------------------------
If you are already using Solr 4.3 or 4.3.1, Solr 4.4 should not present any major problems.
However, you should review the [{{CHANGES.txt}}|http://lucene.apache.org/solr/4_4_0/changes/Changes.html]
file found in your Solr package for changes and updates that may effect your existing implementation.

h2. Upgrading from 4.3.x

If you are upgrading directly from Solr 4.3.0 to 4.4, Solr 4.3.1 included several major bug
fixes, which are also included in Solr 4.4.  Notable fixes: the new shard splitting feature
in particular was made much more stable, with five fixed bugs; {{solr.xml}} {{sharedLib}}
didn't work in Solr 4.3.0; and SolrCore reloading was broken when the UpdateLog was enabled
- this last bug affected both Solr 4.2.1 and 4.3.0.

Solr 4.3.0 introduced a new {{solr.xml}} "discovery" mode and format, which is now the default
in Solr 4.4.  The pre-4.3.0 {{solr.xml}} "legacy" mode and format will no longer be supported
in Solr 5.0.  For a thorough treatment of these issues, including how to migrate from "legacy"
to "discovery" {{solr.xml}} configurations, see [Solr Cores and solr.xml].

The new ["deleteshard" collections API|Collections+API#CollectionsAPI-DeleteaShard] unloads
all replicas of a given shard and then removes it from the cluster state - it will remove
only those shards which are INACTIVE (e.g. post-shard-split parent shards) or have no range
(created for custom sharding).  

More shard splitting bugs were fixed: the "splitshard" API wasn't calling commit on new sub
shards before switching shard states; and multiple bugs related to sub shard recovery and
replication were fixed.

{{TieredMergePolicy}} and the various subtypes of {{LogMergePolicy}} no longer have an explicit
"{{setUseCompoundFile}}" method.  Instead the behavior of new segments is determined by the
{{IndexWriter}} configuration, and the {{MergePolicy}} is only consulted to determine if merge
segments should use the compound file format (based on the value of "{{setNoCFSRatio}}").
 If you have explicitly configured one of these classes using {{<mergePolicy>}} and
include an init arg like this... {code:language=xml|borderStyle=solid|borderColor=#666666}<bool
name="useCompoundFile">true</bool>{code} ...this will now be treated as if you specified...
{code:language=xml|borderStyle=solid|borderColor=#666666}<useCompoundFile>true</useCompoundFile>{code}
...directly on the {{<indexConfig>}} (overriding any value already set using that syntax)
and a warning will be logged to update your configuration.  Users with an explicitly declared
{{<mergePolicy>}} are encouraged to review [the current javadocs for their {{MergePolicy}}
subclass|http://lucene.apache.org/core/4_4_0/core/org/apache/lucene/index/MergePolicy.html]
and review their configured options carefully.  See [SOLR-4941|https://issues.apache.org/jira/browse/SOLR-4941],
[SOLR-4934|https://issues.apache.org/jira/browse/SOLR-4934] and [LUCENE-5038|https://issues.apache.org/jira/browse/LUCENE-5038]
for more information.

The signature of {{LogWatcher.registerListener}} has changed, from {{(ListenerConfig, CoreContainer)}}
to {{(ListenerConfig)}}.  Users implementing their own {{LogWatcher}} classes will need to
change their code accordingly.

{{ByteField}} and {{ShortField}} have been deprecated and will be removed in Solr 5.0. If
you are still using these field types, you should migrate your fields to {{TrieIntField}}.

Finally, the Admin UI now displays the dashboard even if Solr is down.

As with any Solr update, it is recommended that you re-index your content.

h2. Upgrading from Older Versions of Solr

This is a summary of some of the key issues related to upgrading in previous versions of Solr.
 Users upgrading from older versions are strongly encouraged to consult {{CHANGES.txt}} the
details of all changes since the version they are upgrading from.

* As of Solr 4.3 the slf4j/logging jars are no longer included in the Solr webapp to allow
for more flexibility in logging.
* Minor changes were made to the Schema API response format in Solr 4.3
* In Solr 4.1 the method Solr uses to identify node names for SolrCloud was changed.  If you
are using SolrCloud and upgrading from Solr 4.0, you may have issues with unknown or lost
nodes. If this occurs, you can manually set the {{host}} parameter either in {{solr.xml}}
or as a system variable. More information can be found in the section on [SolrCloud].
* If you are upgrading from Solr 3.x, you should familiarize yourself with the [Major Changes
from Solr 3 to Solr 4]. 


{scrollbar}



Stop watching space: https://cwiki.apache.org/confluence/users/removespacenotification.action?spaceKey=solr
Change email notification preferences: https://cwiki.apache.org/confluence/users/editmyemailsettings.action


   

Mime
View raw message