[
https://issues.apache.org/jira/browse/SOLR-17520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-17520:
--------------------------------
Priority: Minor (was: Major)
> CloudSolrClient with HTTP ClusterState shouldn't time-expire recently used
> cache entries
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-17520
> URL: https://issues.apache.org/jira/browse/SOLR-17520
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud, SolrJ
> Reporter: David Smiley
> Priority: Minor
>
> When using CloudSolrClient with HTTP URLs to Solr for the cluster state:
> CloudSolrClient caches a collection's state (DocCollection) for a limited
> time in ExpiringCachedDocCollection. It doesn't matter how
> frequently/recently this collection is used; it'll expire anyway. I think
> instead, the expiration should keep getting pushed back on each use so that
> we don't needlessly ask Solr for the DocCollection every ~minute. The
> possible stale-ness of a DocCollection shall be handled by existing
> "stateVer" mechanisms.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
