[
https://issues.apache.org/jira/browse/SOLR-9063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-9063:
-------------------------------
Assignee: David Smiley
This problem occurs when multiple shards are on the same server/node.
Investigating further, trying to put together a patch either adding a new test
or more likely strengthening some existing tests to sometimes co-host the
shards.
> CloudSolrClient with _route_ shouldn't require collection param to disambig
> cores
> ---------------------------------------------------------------------------------
>
> Key: SOLR-9063
> URL: https://issues.apache.org/jira/browse/SOLR-9063
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud, SolrJ
> Affects Versions: 4.10.4
> Reporter: David Smiley
> Assignee: David Smiley
>
> CloudSolrClient uses {{\_route\_}} to know where to send a request It sorta
> works -- it'll go to an appropriate _node_. But it will only go to the
> correct core on that node if the {{collection}} parameter is explicitly
> added. In another words, it ignores the default collection configured on
> CloudSolrClient. It also seems to ignore "collection" parameter to the
> protected method sendRequest for this purpose too. As I write this, see line
> 1139 on master.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
