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 "NewSolrCloudDesign" by NoblePaul
Date Fri, 19 Aug 2011 06:04:50 GMT
Dear Wiki user,

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

The "NewSolrCloudDesign" page has been changed by NoblePaul:
http://wiki.apache.org/solr/NewSolrCloudDesign?action=diff&rev1=8&rev2=9

  === solr_cluster.properties ===
  
  This are the set of properties which are outside of the regular Solr configuration and is
applicable across all nodes in the cluster:
-  * replication_factor :  The number of replicas of a doc maintained by the cluster
+  * '''replication_factor''' :  The number of replicas of a doc maintained by the cluster
-  * min_writes : Minimum no:of successful writes before the write operation is signaled as
successful . This may me overridden on a per write basis
+  * '''min_writes''' : Minimum no:of successful writes before the write operation is signaled
as successful . This may me overridden on a per write basis
-  * commit_within :  This is the max time within which write operation is visible in a search
+  * '''commit_within''' :  This is the max time within which write operation is visible in
a search
-  * hash_function : The implementation which computes the hash of a given doc
+  * '''hash_function''' : The implementation which computes the hash of a given doc
-  * max_hash_value : The maximum value that a hash_function can output. Theoretically, this
is also the maximum number of partitions the cluster can ever have
+  * '''max_hash_value''' : The maximum value that a hash_function can output. Theoretically,
this is also the maximum number of partitions the cluster can ever have
-  * min_reaction_time : The time before any reallocation/splitting is done after a node comes
up or goes down (in secs)
+  * '''min_reaction_time''' : The time before any reallocation/splitting is done after a
node comes up or goes down (in secs)
-  * min_replica_for_reaction :  If the number of replica nodes go below this threshold the
splitting is triggered even if the min_reaction_time is not met
+  * '''min_replica_for_reaction''' :  If the number of replica nodes go below this threshold
the splitting is triggered even if the min_reaction_time is not met
-  * auto_add_new_nodes :  A Boolean flag. If true, new nodes are automatically used as read
replicas to existing partitions, otherwise, new nodes sit idle until the cluster needs them.
+  * '''auto_add_new_nodes''' :  A Boolean flag. If true, new nodes are automatically used
as read replicas to existing partitions, otherwise, new nodes sit idle until the cluster needs
them.
  
  == Cluster Admin Commands ==
  
  All cluster admin commands run on all nodes at a given path (say /cluster_admin). All nodes
are capable of accepting the same commands and the behavior would be same. These are the public
commands which a user can use to manage a cluster:
-  * init_cluster :  (params : partition) This command is issued after the initial set of
nodes are started. Till this command is issued, the cluster would not accept any read/write
commands
+  * '''init_cluster''' :  (params : partition) This command is issued after the initial set
of nodes are started. Till this command is issued, the cluster would not accept any read/write
commands
-  * split_partition : (params : partition,,optional,,). The partition is split into two halves.
If the partition parameter is not supplied, the partition with the largest number of documents
is identified as the candidate.
+  * '''split_partition''' : (params : partition,,optional,,). The partition is split into
two halves. If the partition parameter is not supplied, the partition with the largest number
of documents is identified as the candidate.
-  * add_idle_nodes : This can be used if auto_add_new_nodes=false. This command triggers
the addition of all ‘idle’ nodes to the cluster.
+  * '''add_idle_nodes''' : This can be used if auto_add_new_nodes=false. This command triggers
the addition of all ‘idle’ nodes to the cluster.
-  * move_partition : (params :  partition, from, to). Move the given partition from a given
node from to another node
+  * '''move_partition''' : (params :  partition, from, to). Move the given partition from
a given node from to another node
-  * command_status :(params : completion_id,,optional,,) . All the above commands are asynchronous
and returns with a completion_id . This command can be used to know the status of a particular
running command or all the current running commands
+  * '''command_status''' :(params : completion_id,,optional,,) . All the above commands are
asynchronous and returns with a completion_id . This command can be used to know the status
of a particular running command or all the current running commands
-  * status : (params : partition,,optional,,) Shows the list of partitions and for each partition,
the following info is provided
+  * '''status''' : (params : partition,,optional,,) Shows the list of partitions and for
each partition, the following info is provided
    * leader node
    * nodes list
    * doc count

Mime
View raw message