[SOLR-14630] CloudSolrClient doesn't pick correct core when server contains more shards

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 8.5.1, 8.5.2
• Fix Version/s: 9.3
• Component/s: SolrCloud, SolrJ
• Assignee: David Smiley
• Reporter: Ivan Djurasevic
• Created: 06/Jul/20 17:36
• Updated: 21/Jul/23 20:40
• Resolved: 31/May/23 12:43

Description

Precondition: create collection with 4 shards on one server.

During search and update, solr cloud client picks wrong core even route exists in query param. In BaseSolrClient class, method sendRequest, 

 

sortedReplicas.forEach( replica -> {
  if (seenNodes.add(replica.getNodeName())) {
    theUrlList.add(ZkCoreNodeProps.getCoreUrl(replica.getBaseUrl(), joinedInputCollections));
  }
});

 

Previous part of code adds base url(localhost:8983/solr/collection_name) to theUrlList, it doesn't create core address(localhost:8983/solr/core_name). If we change previous code to:

sortedReplicas.forEach(replica -> {
    if (seenNodes.add(replica.getNodeName())) {
        theUrlList.add(replica.getCoreUrl());
    }
});

Solr cloud client picks core which is defined with  route parameter.

 

  

Issue Links

• links to: GitHub Pull Request #1646