lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Solr Wiki] Trivial Update of "SolrCloud" by stevencasey
Date Mon, 04 Feb 2013 00:56:02 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "SolrCloud" page has been changed by stevencasey:

added codeblock highlight to _version_ ffield and changed line about cores to highlight change
is not in solrconfig.xml

  === schema.xml ===
  You must have a _version_ field defined:
+ {{{
  <field name="_version_" type="long" indexed="true" stored="true" multiValued="false"/>
+ }}}
  === solrconfig.xml ===
  You must have an UpdateLog defined - this should be defined in the updateHandler section.
@@ -264, +266 @@

      <requestHandler name="/admin/" class="solr.admin.AdminHandlers" />
- And you must leave the admin path in solr.xml as the default:
- {{{
-     <cores adminPath="/admin/cores"
- }}}
  The DistributedUpdateProcessor is part of the default update chain and is automatically
injected into any of your custom update chains. You can still explicitly add it yourself as
@@ -280, +277 @@

  If you do not want the '''DistributedUpdateProcessFactory''' auto injected into your chain
(say you want to use SolrCloud functionality, but you want to distribute updates yourself)
then specify the following update processor factory in your chain: '''NoOpDistributingUpdateProcessorFactory'''
+ === solr.xml ===
+ You must leave the admin path as the default:
+ {{{
+     <cores adminPath="/admin/cores"
+ }}}
  == Re-sizing a Cluster ==
  You can control cluster size by passing the numShards when you start up the first SolrCore
in a collection. This parameter is used to auto assign which shard each instance should be
part of. Any SolrCores that you start after starting numShards instances are evenly added
to each shard as replicas (as long as they all belong to the same collection).

View raw message