[
https://issues.apache.org/jira/browse/SOLR-15124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl reopened SOLR-15124:
--------------------------------
Re-opening as this seems to have caused a reproducible \@Nightly test failure
in {{{}org.apache.solr.handler.admin.ThreadDumpHandlerTest
(testOwnableSyncWaiting){}}}:
[https://ci-builds.apache.org/job/Solr/job/Solr-NightlyTests-main/323/]
{code:java}
gradlew test --tests ThreadDumpHandlerTest.testOwnableSyncWaiting
-Dtests.seed=89AA196C0254FAD7 -Dtests.multiplier=2 -Dtests.nightly=true
-Dtests.slow=true
-Dtests.linedocsfile=/home/jenkins/jenkins-slave/workspace/Solr/Solr-NightlyTests-main/test-data/enwiki.random.lines.txt
-Dtests.locale=nyn -Dtests.timezone=America/Godthab -Dtests.asserts=true
-Dtests.file.encoding=UTF-8 {code}
and
{code:java}
gradlew test --tests ThreadDumpHandlerTest.testMonitorBlocked
-Dtests.seed=89AA196C0254FAD7 -Dtests.multiplier=2 -Dtests.nightly=true
-Dtests.slow=true
-Dtests.linedocsfile=/home/jenkins/jenkins-slave/workspace/Solr/Solr-NightlyTests-main/test-data/enwiki.random.lines.txt
-Dtests.locale=nyn -Dtests.timezone=America/Godthab -Dtests.asserts=true
-Dtests.file.encoding=UTF-8 {code}
> Remove node/container level admin handlers from ImplicitPlugins.json (core
> level).
> ----------------------------------------------------------------------------------
>
> Key: SOLR-15124
> URL: https://issues.apache.org/jira/browse/SOLR-15124
> Project: Solr
> Issue Type: Task
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Blocker
> Labels: newdev
> Fix For: 9.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> There are many very old administrative RequestHandlers registered in a
> SolrCore that are actually JVM / node / CoreContainer level in nature. These
> pre-dated CoreContainer level handlers. We should (1) remove them from
> ImplictPlugins.json, and (2) make simplifying tweaks to them to remove that
> they work at the core level. For example LoggingHandler has two constructors
> and a non-final Watcher because it works in these two modalities. It need
> only have the one that takes a CoreContainer, and Watcher will then be final.
> /admin/threads
> /admin/properties
> /admin/logging
> Should stay because has core-level stuff:
> /admin/plugins
> /admin/mbeans
> This one:
> /admin/system -- SystemInfoHandler
> returns "core" level information, and also node level stuff. I propose
> splitting this one to a CoreInfoHandler to split the logic. Maybe a separate
> issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
