[
https://issues.apache.org/jira/browse/SOLR-18434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris M. Hostetter updated SOLR-18434:
--------------------------------------
Summary: SolrRequest.getPreferredNodes() used very inconsistently in
CloudSolrClient (was: SolrRequest.getPreferredNodes() used very inconsistently)
> SolrRequest.getPreferredNodes() used very inconsistently in CloudSolrClient
> ---------------------------------------------------------------------------
>
> Key: SOLR-18434
> URL: https://issues.apache.org/jira/browse/SOLR-18434
> Project: Solr
> Issue Type: Sub-task
> Reporter: Chris M. Hostetter
> Priority: Major
>
> (See parent Jira for larger context)
> {{SolrRequest.getPreferredNodes()}} is only respected by {{CloudSolrClient}}
> in the specific case of a request that is {{true == requresCollection)}}
> *_AND_* {{getApiVersion() != V2}}
> This is very strange, since nothing in the docs for
> {{SolrRequest.setPreferredNode()}} implies that it's only for (non V2)
> collection specific requests.
> It's particularly strange since using {{SolrRequest.setPreferredNode()}}
> seems like the most obvious course of action for users trying to follow the
> recommended instructions (of trying to send collection admin requests to a
> consistent node) when disabling the overseer.
> ----
> I see no reason why {{SolrRequest.getPreferredNodes()}} shouldn't be
> respected for *ALL* types of requests?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
