[
https://issues.apache.org/jira/browse/SOLR-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505547#comment-13505547
]
Per Steffensen commented on SOLR-4114:
--------------------------------------
bq. could not you do same thing as Elastic Search. Build index with number of
shards (initial number is 5). If there is 1 machine in cluster, then all shards
are on this machine. If you add more machines, they will move to other
machines. It is way simple for administration.
This moving shards around as more Solr servers join the cluster is the easiest
way to provide elasticity (as I mentioned above somewhere). That is one of the
reasons, that I want to be able to run multiple shards for a collection on the
same Solr server. In that way you will have shards already to move to other
Solrs that might join the cluster later.
In Solr, right now, we dont have the abillity to move shards from one server to
another (ES has it), but in order to be able to bennefit from such a future
feature, you will need to be able have multiple shards on one Solr server.
Alternatively you have to go split a shard, but that is much harder, and should
only be used if you did not forsee, when you created your collection, that you
would add more servers later, and therefore created your collection with
multiple shards per server.
> Collection API: Allow multiple shards from one collection on the same Solr
> server
> ---------------------------------------------------------------------------------
>
> Key: SOLR-4114
> URL: https://issues.apache.org/jira/browse/SOLR-4114
> Project: Solr
> Issue Type: New Feature
> Components: multicore, SolrCloud
> Affects Versions: 4.0
> Environment: Solr 4.0.0 release
> Reporter: Per Steffensen
> Assignee: Per Steffensen
> Labels: collection-api, multicore, shard, shard-allocation
> Attachments: SOLR-4114.patch, SOLR-4114.patch
>
>
> We should support running multiple shards from one collection on the same
> Solr server - the run a collection with 8 shards on a 4 Solr server cluster
> (each Solr server running 2 shards).
> Performance tests at our side has shown that this is a good idea, and it is
> also a good idea for easy elasticity later on - it is much easier to move an
> entire existing shards from one Solr server to another one that just joined
> the cluter than it is to split an exsiting shard among the Solr that used to
> run it and the new Solr.
> See dev mailing list discussion "Multiple shards for one collection on the
> same Solr server"
--
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
