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 EricPugh
Date Mon, 17 Dec 2012 18:02:01 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 EricPugh:
http://wiki.apache.org/solr/SolrCloud?action=diff&rev1=83&rev2=84

Comment:
Should I say this is a Solr 4.1 change?   

   * '''name''': The name of the collection to be created
   * '''numShards''': The number of shards (sometimes called slices) to be created as part
of the collection
   * '''replicationFactor''': The number of "additional" shard-replica (sometimes called shards)
to be created for each shard. Set it to 0 to have "one shard-replica for each of your shards".
Set to 1 to have "two shard-replica for each of your shards" etc. With a value of 0 your data
will not be replicated
-  * '''maxShardsPerNode''' (not in 4.0.0 and not even committet yet - see SOLR-4114): A create
operation will spread numShards*(replicationFactor+1) shard-replica across your live Solr
nodes - fairly distributed, and never two shard-replica of the same shard on the same Solr
node. If a Solr is not live at the point in time where the create operation is carried out,
it will not get any shard-replica of the new collection. To prevent too many shard-replica
being created on a single Solr node, use maxShardsPerNode to set a limit for how many shard-replica
the create operation is allowed to create on each node - default is 1. If it cannot fit the
entire collection (numShards*(replicationFactor+1) shard-replica) on you live Solrs it will
not create anything at all.
+  * '''maxShardsPerNode''' : A create operation will spread numShards*(replicationFactor+1)
shard-replica across your live Solr nodes - fairly distributed, and never two shard-replica
of the same shard on the same Solr node. If a Solr is not live at the point in time where
the create operation is carried out, it will not get any shard-replica of the new collection.
To prevent too many shard-replica being created on a single Solr node, use maxShardsPerNode
to set a limit for how many shard-replica the create operation is allowed to create on each
node - default is 1. If it cannot fit the entire collection (numShards*(replicationFactor+1)
shard-replica) on you live Solrs it will not create anything at all.
-  * '''createNodeSet''' (not in 4.0.0 and not even committet yet - see SOLR-4120): If not
provided the create operation will create shard-replica spread across all of your live Solr
nodes. You can provide the "createNodeSet" parameter to change the set of nodes to spread
the shard-replica across. The format of values for this param is "<node-name1>,<node-name2>,...,<node-nameN>"
- e.g. "localhost:8983_solr,localhost:8984_solr,localhost:8985_solr"
+  * '''createNodeSet''': If not provided the create operation will create shard-replica spread
across all of your live Solr nodes. You can provide the "createNodeSet" parameter to change
the set of nodes to spread the shard-replica across. The format of values for this param is
"<node-name1>,<node-name2>,...,<node-nameN>" - e.g. "localhost:8983_solr,localhost:8984_solr,localhost:8985_solr"
  
  Note: replicationFactor defines the maximum number of replicas created in addition to the
leader from amongst the nodes currently running (i.e. nodes added later will not be used for
this collection). Imagine you have a cluster with 20 nodes and want to add an additional smaller
collection to your installation with 2 shards, each shard with a leader and two replicas.
You would specify a replicationFactor=2. Now six of your nodes will host this new collection
and the other 14 will not host the new collection.
  

Mime
View raw message