[
https://issues.apache.org/jira/browse/SOLR-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529093#comment-13529093
]
Per Steffensen commented on SOLR-4114:
--------------------------------------
Thanks Mark
Guess what is left is:
* Decide if you want to enable the call to "checkCollectionIsNotCreated" and
set the wait in it to 10 sec (or so), or if you are prepared to drop this part
of the test, now that you got the OverseerCollectionProcessorTest
* Maybe make a comment on SOLR-4043 that you ought to modify the
BasicDistributedZkTest.testCollectionsAPI test as a part of solving that issue.
* Add the checkNoTwoShardsUseTheSameIndexDir thing if you (also) find it
usefull (see above)
* Add SOLR-4114_mocking_OverseerCollectionProcessorTest_branch_4x.patch
But you probably want to read through the (last of the) comments above to make
sure we didnt miss something we promissed (eash other and/or Robert Muir) :-)
Regards, Per Steffensen
> 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_mocking_OverseerCollectionProcessorTest_branch_4x.patch,
> SOLR-4114.patch, SOLR-4114.patch, SOLR-4114.patch, SOLR-4114.patch,
> SOLR-4114_trunk.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
