[SOLR-10733] Rule-based Replica Placement not working correct

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 6.5.1
• Component/s: Rules, SolrCloud
• Assignee: Noble Paul
• Reporter: Bernd Fehling
• Created: 23/May/17 14:17
• Updated: 06/Apr/20 11:25
• Resolved: 06/Apr/20 11:25

Description

A setup of a SolrCloud with 6 nodes on 3 server e.g.:

server1:8983 , server1:7574
server2:8983 , server2:7574
server3:8983 , server3:7574

and a command for creating a new collection with rule:

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

should create a collection with 3 shards and least a shard1 with two different nodes running on port 8983.

shard1 --> server_x:8983 ,  server_y:8983

A even more restrictive rule like

rule=shard:shard1,replica:<2,port:8983&rule=shard:shard3,replica:<2,port:7574

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.

Issue Links

• incorporates: SOLR-12741 Nuke rule based replica placement strategy in Lucene/Solr 8.0
• is related to: SOLR-11476 Solr seems to ignore replica placement rules
• is related to: SOLR-11634 Create collection doesn't respect `maxShardsPerNode`
• is related to: SOLR-11005 inconsistency when maxShardsPerNode used along with policies