[
https://issues.apache.org/jira/browse/SOLR-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529976#comment-13529976
]
Mark Miller commented on SOLR-4114:
-----------------------------------
I don't often run precommit - takes too long - but I generally do when adding
new dependencies because i know there will be license stuff. Jenkins will catch
it even if we dont before commit though.
You have to extend LuceneTestCase because thats what hooks you into our "test
framework" I believe - eg it enforces things like setup and teardown calling
super and a ton of other nice stuff.
If you don't do it, jenkins will complain and fail.
I'll look at SOLR-4120.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
