[
https://issues.apache.org/jira/browse/SOLR-17921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18021735#comment-18021735
]
Houston Putman commented on SOLR-17921:
---------------------------------------
SOLR-17601 - I really like that idea, but the refetching should be done
asynchronously regardless. I think this is a good intermediate solution.
{quote}The same is true of a collection's state; no? {quote}
So yes, technically, but then the CloudSolrClient takes care of caching that
information itself. Ideally the caching mechanism of the collection state, the
aliases, and the liveNodes would all be managed the same way, but that is a
much more invasive change and something likely better for 10.0 than it is for
9.10.
> BaseHttpClusterStateProvider should prefetch refreshes of liveNodes
> -------------------------------------------------------------------
>
> Key: SOLR-17921
> URL: https://issues.apache.org/jira/browse/SOLR-17921
> Project: Solr
> Issue Type: New Feature
> Components: SolrJ
> Reporter: Houston Putman
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently the BaseHttpClusterStateProvider synchronously updates the
> liveNodes when a request comes in and the cached liveNodes has expired. There
> should be an asynchronous re-fetching of this data so that requests are not
> blocked after expiration.
> Also the getLiveNodes() method was made synchronized in SOLR-17607, which is
> very expensive for multiThreaded solrJ applications, as getLiveNodes() is
> called very often. So that needs to be fixed to only block when the liveNodes
> need to be fetched.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
