You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by Apache Wiki <wi...@apache.org> on 2013/05/31 07:07:55 UTC

[Solr Wiki] Update of "SolrCloud" by ShalinMangar

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 ShalinMangar:
https://wiki.apache.org/solr/SolrCloud?action=diff&rev1=104&rev2=105

Comment:
Added note to not use shard splitting with custom hashing

   * '''collection''': The name of the collection
   * '''shard''': The shard to be split
  
+ This command cannot be used by clusters with custom hashing because such clusters do not rely on a hash range. It should only be used by clusters having "plain" or "compositeId" router.
+ 
  The SPLITSHARD command will create two new shards by splitting the given shard's index into two pieces. The split is performed by dividing the shard's range into two equal partitions and dividing up the documents in the parent shard according to the new sub-ranges. This is a synchronous operation. The new shards will be named by appending _0 and _1 to the parent shard name e.g. if shard=shard1 is to be split, the new shards will be named as shard1_0 and shard1_1. Once the new shards are created, they are set active and the parent shard is set to inactive so that no new requests are routed to the parent shard.
  
  This feature allows for seamless splitting and requires no down-time. The parent shard is not removed and therefore no data is removed. It is up to the user of the command to unload the shard using the new APIs in SOLR-4693 (under construction).
  
- This feature is being developed as part of the jira issue SOLR-3755 and will be released with Solr 4.3
+ This feature was released with Solr 4.3 however due to bugs found after 4.3 release, it is recommended that you wait for release 4.3.1 before using this feature.
  
  == Creating cores via CoreAdmin ==
  New Solr cores may also be created and associated with a collection via CoreAdmin.