[
https://issues.apache.org/jira/browse/SOLR-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529791#comment-13529791
]
Per Steffensen commented on SOLR-4114:
--------------------------------------
bq. Great patch! I just had to make a couple small tweaks to make the policeman
happy - added license files for the test jars, changed the new test to extend
LuceneTestCase. Good stuff found by the long but useful precommit ant target.
Yes, I do not do precommit test before sending a patch. Of course I will do
before committing myself if/when I become committer.
Just out of curiosity, why do tests HAVE to extend LuceneTestCase?
bq. I think that covers all of your points Per - let me know
Checking only on branch_4x, hopeing that you did the "exact" same changes on
trunk. Updated my local checkout of branch_4x, made a check to see if
everything seemed to be there. It was. I am ready to close this ticket.
> 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: Mark Miller
> Labels: collection-api, multicore, shard, shard-allocation
> Fix For: 4.1, 5.0
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
