[jira] [Commented] (SOLR-14423) static caches in StreamHandler ought to move to CoreContainer lifecycle

["David Smiley (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922888#comment-17922888 ] 

David Smiley commented on SOLR-14423:
-------------------------------------

Following up to those here; I'm discussing with others in SOLR-17630 about deprecating CoreContainer.getSolrClientCache in lieu of a node CloudSolrClient and node Http2SolrClient (that can use any URL to talk to whoever) for general inter-node use.  SCC then becomes something only needed by the streaming expressions framework, so would likely go back there.  If you have thoughts, please raise them there.

> static caches in StreamHandler ought to move to CoreContainer lifecycle
> -----------------------------------------------------------------------
>
>                 Key: SOLR-14423
>                 URL: https://issues.apache.org/jira/browse/SOLR-14423
>             Project: Solr
>          Issue Type: Bug
>          Components: streaming expressions
>            Reporter: David Smiley
>            Assignee: Andrzej Bialecki
>            Priority: Major
>             Fix For: 8.6
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> StreamHandler (at "/stream") has several statically declared caches.  I think this is problematic, such as in testing wherein multiple nodes could be in the same JVM.  One of them is more serious -- SolrClientCache which is closed/cleared via a SolrCore close hook.  That's bad for performance but also dangerous since another core might want to use one of these clients!
> CC [~jbernste]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org