Hoss Man created SOLR-8907:
------------------------------
Summary: add features to MiniSolrCloudCluster to make
shard/leader/replica placement more reproducible
Key: SOLR-8907
URL: https://issues.apache.org/jira/browse/SOLR-8907
Project: Solr
Issue Type: Improvement
Reporter: Hoss Man
I think MiniSolrCloudCluster would be greatly improved if (by default)
collections created for test purposes had predictable shard/leader/core
assignment across the jetty instances that are spun up. Even though the port#s
used by the jettys will obviously vary every time a test is run, ideally a
given seed should ensure that the following are all consistent:
* the node_name used by each JettySolrRunner
* which nodes host which shards
* the core names use on each jetty instance
* which core is the leader for each shard
Obviously this wouldn't make sense for tests where the entire purpose is to
ensure that the automatic assignment of these things works properly when
creating a collection, or when explicitly testing things like "preferedLeader",
but for tests of non-collection API related features (ie: update requests,
search requests, sorting, etc...) where the test setup already takes advantage
of methods like {{MiniSolrCloudCluster.createCollection(...)}} as a short cut
to using the API directly, this type of consistency would make potential test
failures a lot more reproducible && easier to diagnose.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
