[
https://issues.apache.org/jira/browse/SOLR-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694670#comment-13694670
]
Noble Paul commented on SOLR-4221:
----------------------------------
Ideally a user would want new shards to go to new nodes so that the existing
nodes are not overloaded. Now it is not possible to achieve it. If I start a
node before t5he command is issued it would just join some random shard and it
is taken up. If I issue the CREATESHARD command before adding nodes it
will/should fail saying insufficient nodes .
Actually, it is relevant for SPLITSHARDas well. Now the new shards created will
go and live in an already loaded node.
The proposed behavior is this. If I startup a node w/o specifying the
collection , it would just be a part of the live nodes and no shard and
collection should be assigned to it. So when a new shard has to be created ,
the command can lookup and see if there are unutilized live nodes and it can
be assigned there
> Custom sharding
> ---------------
>
> Key: SOLR-4221
> URL: https://issues.apache.org/jira/browse/SOLR-4221
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
