[
https://issues.apache.org/jira/browse/SOLR-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510351#comment-13510351
]
Per Steffensen commented on SOLR-4114:
--------------------------------------
bq. I suppose a 10 second sleep is more agreeable, but these things add up and
and I'd rather come up with a better test.
I would rather too, but believe it is hard to make sure something does not
happen, without giving it a chance to happen, and check that it did not. So
there is no better way of testing it, as I see it. At least if you want this
kind of integration-ish test, where you start a full system and do something to
it as if you where a real client acting against a real system. And I like this
kind of tests. If we go do a more unit-test-ish test directly on
OverseerCollectionProcessor we might be able to do something faster, but it
will not ensure the correct system-level functionality to nearly the same
degree.
I think you should commit with a 10-20 sec wait, and then if you (or someone
else) can come up with a faster way for testing it properly, it is fine for me
to make the change. I do not believe I will be able to come up with a proper
test of this that is faster. But protect the feature "the slow way" until
someone comes up with a faster way of testing.
> 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, 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
