[
https://issues.apache.org/jira/browse/SOLR-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698158#comment-13698158
]
Shai Erera commented on SOLR-4221:
----------------------------------
Exactly. New nodes mean just more resources, I don't think they should affect
the number of resources the search cluster needs, only define how many
resources are available. Conceptually, we could have a cost function which
takes into account the node's RAM/CPU/Disk + indexes size (GBs, #docs), maybe
even based on performance history, and assign indexes to nodes following that
cost function.
The way I picture it (and I don't know how to map that to Solr jargon):
* A new node comes up, broadcasts "I'm alive"
* Maybe communicates with other "overbooked" nodes to transfer indexes over
* A ClusterBalancer (Overseer?) periodically checks if the cluster can be
better balanced (e.g. splitting shards, moving indexes)
* Maybe even we drop numShards entirely and make this a completely dynamic and
automatic setting (or at least optional), but this is for future work
> 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
