Bernd Fehling created SOLR-10733:
------------------------------------
Summary: Rule-based Replica Placement not working correct
Key: SOLR-10733
URL: https://issues.apache.org/jira/browse/SOLR-10733
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: Rules, SolrCloud
Affects Versions: 6.5.1
Reporter: Bernd Fehling
A setup of a SolrCloud with 6 nodes on 3 server e.g.:
{code}
server1:8983 , server1:7574
server2:8983 , server2:7574
server3:8983 , server3:7574
{code}
and a command for creating a new collection with rule:
{code}
http://localhost:8983/solr/admin/collections?action=CREATE&name=boss&;
collection.configName=boss_configs&numShards=3&replicationFactor=2&
maxShardsPerNode=1&rule=shard:shard1,replica:<2,port:8983
{code}
should create a collection with 3 shards and least a shard1 with two different
nodes running on port 8983.
{code}
shard1 --> server_x:8983 , server_y:8983
{code}
A even more restrictive rule like
{code}
rule=shard:shard1,replica:<2,port:8983&rule=shard:shard3,replica:<2,port:7574
{code}
should also resolve to a solution because if it really checks all permutations
accross shards/replicas/ports and available nodes it should be able to solve
this.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
