[
https://issues.apache.org/jira/browse/SOLR-17153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835736#comment-17835736
]
ASF subversion and git services commented on SOLR-17153:
--------------------------------------------------------
Commit 09e8d0cb0d938711e9f65636bff1d45e49512eed in solr's branch
refs/heads/main from aparnasuresh85
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=09e8d0cb0d9 ]
SOLR-17153: Fix IndexOutOfBoundsException, add bats test (#2393)
Resolve IndexOutOfBoundsException, a regression from the first change in this
issue.
* Call resolveDocCollection inside getCoreByCollection
* New BATS test to check URLs that the Solr Admin UI (or a user trying to
navigate to such) might use
> CloudSolrClient should not throw "Collection not found" with an out-dated
> ClusterState
> --------------------------------------------------------------------------------------
>
> Key: SOLR-17153
> URL: https://issues.apache.org/jira/browse/SOLR-17153
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ
> Reporter: David Smiley
> Priority: Major
> Time Spent: 5h 50m
> Remaining Estimate: 0h
>
> Today, CloudSolrClient will locally fail if it's asked to send a request to a
> collection that it thinks does not exist due to its local ClusterState view
> being out-of-date. We shouldn't fail! And most SolrCloud tests should then
> remove their waitForState calls that follow collection creation! Other stale
> state matters are out-of-scope.
> Proposal: CloudSolrClient shouldn't try and be too smart. Always route a
> request to Solr (any node); don't presume its state is up-to-date. Maybe,
> after a response is received, it can check if its state has been updated and
> if not then explicitly get a new state. Or not if that's too complicated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
