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 Mark Miller: http://wiki.apache.org/solr/SolrCloud?action=diff&rev1=37&rev2=38 == Required Config == - * WIP * - All of the required config is already setup in the example configs shipped with Solr. === schema.xml === @@ -215, +213 @@ You must have an UpdateLog defined; the sample puts this in the !DirectUpdateHandler2 updateHandler element. - + {{{ <!-- Enables a transaction log, currently used for real-time get. "dir" - the target directory for transaction logs, defaults to the solr data directory. --> <updateLog> <str name="dir">${solr.data.dir:}</str> </updateLog> - + }}} You must have a replication handler called /replication defined: + {{{ - <!-- Solr Replication for SolrCloud Recovery - - This is the config need for SolrCloud's recovery replication. - --> - <requestHandler name="/replication" class="solr.ReplicationHandler" startup="lazy" /> + <requestHandler name="/replication" class="solr.ReplicationHandler" startup="lazy" /> - + }}} You must have a realtime get handler called /get defined: - + {{{ - <requestHandler name="/get" class="solr.RealTimeGetHandler"> + <requestHandler name="/get" class="solr.RealTimeGetHandler"> - <lst name="defaults"> + <lst name="defaults"> - <str name="omitHeader">true</str> + <str name="omitHeader">true</str> </lst> - </requestHandler> + </requestHandler> - + }}} + You must have the admin handlers defined: + {{{ + <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, but if you define a custom update chain you would like to use with SolrCloud, you must put the DistributedUpdateProcessor in that chain: + {{{ <updateRequestProcessorChain name="sample"> - <processor class="solr.LogUpdateProcessorFactory" /> + <processor class="solr.LogUpdateProcessorFactory" /> - <processor class="solr.DistributedUpdateProcessorFactory"/> + <processor class="solr.DistributedUpdateProcessorFactory"/> - <processor class="my.package.UpdateFactory"/> + <processor class="my.package.UpdateFactory"/> - <processor class="solr.RunUpdateProcessorFactory" /> + <processor class="solr.RunUpdateProcessorFactory" /> - </updateRequestProcessorChain> + </updateRequestProcessorChain> + }}} - - ...coming... == 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).
