lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <>
Subject [jira] [Commented] (SOLR-4221) Custom sharding
Date Tue, 02 Jul 2013 19:51:20 GMT


Noble Paul commented on SOLR-4221:

bq.Another usecase is to have multiple collections, each with different number of shards and
different #replicas.

This is why I feel we should not automatically create cores in nodes that come up. The best
thing to do is

Any new node will just not participate in any collection (unless a shard has fewer nodes than

There should be an explicit ASSIGN_NODE command to add/remove nodes to/from a shard.  
It should be possible to do an ASSIGN_NODE without specifying a nodename in which case the
overseer would look for free nodes in the cluster and add to the specified shard 
when a new shard is created by CREATESHARD command or when a SPLITSHARD command this nodes
could be automatically be taken up. 

> Custom sharding
> ---------------
>                 Key: SOLR-4221
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Yonik Seeley
>            Assignee: Noble Paul
>         Attachments: SOLR-4221.patch
> Features to let users control everything about sharding/routing.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message