[
https://issues.apache.org/jira/browse/SOLR-16615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17656275#comment-17656275
]
David Smiley commented on SOLR-16615:
-------------------------------------
Talking out loud here....
This will be a big change because lots of components implement SolrCoreAware;
this has big implications. Looking at SearchHandler, an implementer of
SolrCoreAware as an example, I see it wants access to other plugins like
SearchComponent impls. These are not instantiated/living on the ConfigSet but
are living in SolrCore. Perhaps this means, we need to make SolrCore light and
instead move things to the ConfigSet. But what about plugins that may need to
actually exist on a SolrCore because it is tied to a core data directory, say,
or that initializes itself by reading from the index? UpdateHandler, having
access to the UpdateLog may be such a component. But given that UH (despite
its name) isn't a RequestHandler (and thus may be misnamed; ha!) -- maybe this
JIRA should be scoped only to RequestHandler and sub-components, as this is
what is pertinent related to JAX-RS. Still, this is hard! What of
ReplicationHandler, which reads the index, sets up polling, etc.? Wow... such
a change doesn't make sense on 9x; it'd be main only.
Maybe JAX-RS/Jersey could create its own endpoint/handler things at the
ConfigSet level but then at actual request execution time, we delegate out to
core handlers? I don't know enough about Jersey yet to dig deeper.
Is there another angle/approach on this I have not considered?
> Colocated cores with the same configset should share resources
> --------------------------------------------------------------
>
> Key: SOLR-16615
> URL: https://issues.apache.org/jira/browse/SOLR-16615
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Jason Gerlowski
> Priority: Minor
> Labels: API, performance
>
> Currently, each core parses solrconfig.xml and instantiates its own copy of
> various plugins (v2 'Api' instances, RequestHandlers, etc.) or plugin-related
> objects (e.g. Jersey "ApplicationHandlers").
> Usually this is fine, but when many cores on a Solr node share the same
> configset, this duplication can become wasteful and have considerable impacts
> on node startup and core reload time.
> We should investigate whether some of these solrconfig.xml-driven entities
> can be shared by cores with the same configset that live in the same JVM.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
