[
https://issues.apache.org/jira/browse/SOLR-16615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679958#comment-17679958
]
Chris M. Hostetter commented on SOLR-16615:
-------------------------------------------
This seems related and bad...
{noformat}
Build: https://jenkins.thetaphi.de/job/Solr-main-Windows/2203/
Java: 64bit/hotspot/jdk-18 -XX:-UseCompressedOops -XX:+UseG1GC
929 tests failed.
FAILED:
org.apache.solr.AnalysisAfterCoreReloadTest.testStopwordsAfterCoreReload
Error Message:
org.apache.solr.core.SolrCoreInitializationException: SolrCore 'collection1' is
not available due to init failure:
Cannot invoke
"org.apache.solr.jersey.JerseyAppHandlerCache.computeIfAbsent(String,
java.util.function.Supplier)"
because the return value of
"org.apache.solr.core.CoreContainer.getAppHandlerCache()" is null
...
FAILED: org.apache.solr.BasicFunctionalityTest.testRequestHandlerBaseException
Error Message:
org.apache.solr.core.SolrCoreInitializationException: SolrCore 'collection1' is
not available due to init failure:
Cannot invoke
"org.apache.solr.jersey.JerseyAppHandlerCache.computeIfAbsent(String,
java.util.function.Supplier)"
because the return value of
"org.apache.solr.core.CoreContainer.getAppHandlerCache()" is null
...
FAILED:
org.apache.solr.analysis.TestWordDelimiterFilterFactory.testNoGenerationEdgeCase
Error Message:
org.apache.solr.core.SolrCoreInitializationException: SolrCore 'collection1' is
not available due to init failure:
Cannot invoke
"org.apache.solr.jersey.JerseyAppHandlerCache.computeIfAbsent(String,
java.util.function.Supplier)"
because the return value of
"org.apache.solr.core.CoreContainer.getAppHandlerCache()" is null
Stack Trace:
org.apache.solr.core.SolrCoreInitializationException: SolrCore 'collection1' is
not available due to init failure:
Cannot invoke
"org.apache.solr.jersey.JerseyAppHandlerCache.computeIfAbsent(String,
java.util.function.Supplier)"
because the return value of
"org.apache.solr.core.CoreContainer.getAppHandlerCache()" is null
at
__randomizedtesting.SeedInfo.seed([BFA19006A9931CEA:30479E26D2769E0A]:0)
at
app//org.apache.solr.core.CoreContainer.getCore(CoreContainer.java:2194)
at
app//org.apache.solr.core.CoreContainer.getCore(CoreContainer.java:2167)
at
app//org.apache.solr.util.TestHarness.getCoreInc(TestHarness.java:278)
at app//org.apache.solr.util.TestHarness.update(TestHarness.java:295)
at
app//org.apache.solr.util.BaseTestHarness.checkUpdateStatus(BaseTestHarness.java:270)
at
app//org.apache.solr.util.BaseTestHarness.validateUpdate(BaseTestHarness.java:238)
at
app//org.apache.solr.SolrTestCaseJ4.checkUpdateU(SolrTestCaseJ4.java:989)
at app//org.apache.solr.SolrTestCaseJ4.assertU(SolrTestCaseJ4.java:971)
at app//org.apache.solr.SolrTestCaseJ4.assertU(SolrTestCaseJ4.java:966)
at
app//org.apache.solr.analysis.TestWordDelimiterFilterFactory.testNoGenerationEdgeCase(TestWordDelimiterFilterFactory
.java:78)
{noformat}
> 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
> Time Spent: 1h 50m
> 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: [email protected]
For additional commands, e-mail: [email protected]
