[
https://issues.apache.org/jira/browse/SOLR-16615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682000#comment-17682000
]
ASF subversion and git services commented on SOLR-16615:
--------------------------------------------------------
Commit 73c938ad2ce70a91e81848f2e810315a273bb7d4 in solr's branch
refs/heads/main from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=73c938ad2ce ]
SOLR-16615: Reinstate Jersey app-per-configset (#1314)
Previously reverted due to a large bug that crept in while resolving
some merge conflicts, this PR adds the app-per-configset code back.
Jersey 'ApplicationHandlers' are now shared by cores in the same JVM
with the same configset.
> 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
> Reporter: Jason Gerlowski
> Priority: Minor
> Labels: API, performance
> Time Spent: 8h 10m
> Remaining Estimate: 0h
>
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
