lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "SolrCloud" by Mark Miller
Date Sat, 07 Jul 2012 21:16:20 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 Mark Miller:
http://wiki.apache.org/solr/SolrCloud?action=diff&rev1=47&rev2=48

     </updateRequestProcessorChain>
  }}}
  
- 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
+ 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'''
  
  == 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).
@@ -292, +292 @@

  || zkHost || No default || value ||
  || zkClientTimeout || Defaults to 10000 || value ||
  
- === Config Bootstrap Params ===
- 
- There are two different ways you can use system properties to upload your initial configuration
files to ZooKeeper the first time you start Solr. Remember that these are meant to be used
only on first startup or when overwriting configuration files - everytime you start Solr with
these system properties, any current configuration files in ZooKeeper may be overwritten when
'conf set' names match.
- 
- || bootstrap_conf || No default || If you pass -Dbootstrap_conf=true on startup, each SolrCore
you have configured will have it's configuration files automatically uploaded and linked to
the collection that SolrCore is part of ||
- 
- || bootstrap_confdir || No default || If you pass -bootstrap_confdir=<directory> on
startup, that specific directory of configuration files will be uploaded to ZooKeeper with
a 'conf set' name defined by the below system property, collection.configName ||
- || collection.configName || Defaults to configuration1 || Determines the name of the conf
set pointed to by bootstrap_confdir ||
  
  === Other ===
  || shardId || Defaults to being automatically assigned based on numShards || value ||
  
+ == Getting your Configuration Files into ZooKeeper ==
+ 
+ === Config Startup Bootstrap Params ===
+ 
+ There are two different ways you can use system properties to upload your initial configuration
files to ZooKeeper the first time you start Solr. Remember that these are meant to be used
only on first startup or when overwriting configuration files - everytime you start Solr with
these system properties, any current configuration files in ZooKeeper may be overwritten when
'conf set' names match.
+ 
+ 1. 
+ ||bootstrap_conf || No default || If you pass -Dbootstrap_conf=true on startup, each SolrCore
you have configured will have it's configuration files automatically uploaded and linked to
the collection that SolrCore is part of ||
+ 2. 
+ ||bootstrap_confdir || No default || If you pass -bootstrap_confdir=<directory> on
startup, that specific directory of configuration files will be uploaded to ZooKeeper with
a 'conf set' name defined by the below system property, collection.configName ||
+ || collection.configName || Defaults to configuration1 || Determines the name of the conf
set pointed to by bootstrap_confdir ||
+ 
+ === Command Line Util ===
+ 
+ TBD
+ 
  == FAQ ==
  
-  * Q: I'm seeing lot's of session timeout exceptions - what to do?
+  * '''Q:''' I'm seeing lot's of session timeout exceptions - what to do?
-    A: Try raising the ZooKeeper session timeout by editing solr.xml - see the zkClientTimeout
attribute. The minimum session timeout is 2 times your ZooKeeper defined tickTime. The maximum
is 20 times the tickTime. The default tickTime is 2 seconds.
+    '''A:''' Try raising the ZooKeeper session timeout by editing solr.xml - see the zkClientTimeout
attribute. The minimum session timeout is 2 times your ZooKeeper defined tickTime. The maximum
is 20 times the tickTime. The default tickTime is 2 seconds.
+  * '''Q:''' How do I use SolrCloud, but distribute updates myself?
+  * '''A:''' Add the following UpdateProcessorFactory somewhere in your update chain: '''NoOpDistributingUpdateProcessorFactory'''
  

Mime
View raw message