[
https://issues.apache.org/jira/browse/SOLR-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18098548#comment-18098548
]
Chris M. Hostetter commented on SOLR-18317:
-------------------------------------------
Stack trace logged by Solr-10.0.0 when using {{docker run -it --rm -p 8983:8983
solr:10.0.0 --user-managed}} and trying to change the log level in the UI...
{noformat}
2026-07-23 17:04:37.999 INFO (qtp69329761-40-null-31) [ t:null-31]
o.a.s.l.l.Log4j2Watcher Setting log level to 'INFO' for logger: root
2026-07-23 17:04:38.003 ERROR (qtp69329761-40-null-31) [ t:null-31]
o.a.s.h.RequestHandlerBase Server exception =>java.lang.NullPointerException:
Cannot read field "zkStateReader" because the return value of
"org.apache.solr.core.CoreContainer.getZkController()" is null
at
org.apache.solr.handler.admin.AdminHandlersProxy.resolveNodes(AdminHandlersProxy.java:170)
2026-07-23 17:04:38.003 INFO (qtp69329761-40-null-31) [ t:null-31]
o.a.s.s.HttpSolrCall [admin] path=/admin/info/logging
params={nodes=all&set=root:INFO&wt=json&_=1784826261694} status=500 QTime=6
2026-07-23 17:04:38.004 ERROR (qtp69329761-40-null-31) [ t:null-31]
o.a.s.s.HttpSolrCall 500 Exception =>java.lang.NullPointerException: Cannot
read field "zkStateReader" because the return value of
"org.apache.solr.core.CoreContainer.getZkController()" is null
at
org.apache.solr.handler.admin.AdminHandlersProxy.resolveNodes(AdminHandlersProxy.java:170)
{noformat}
Stack trace logged by current branch_10x when using {{./gradlew dev;
./solr/packaging/build/dev/bin/solr start --user-managed}} and trying to make
the same change via the UI...
{noformat}
2026-07-23 17:39:38.433 INFO (qtp65488937-40-null-10) [ t:null-10]
o.a.s.s.HttpSolrCall [admin] path=/admin/info/logging
params={nodes=all&set=root:WARN&wt=json&_=1784827279633} status=500 QTime=4
2026-07-23 17:39:38.433 ERROR (qtp65488937-40-null-10) [ t:null-10]
o.a.s.s.HttpSolrCall 500 Exception
java.lang.NullPointerException: Cannot read field "zkStateReader" because the
return value of "org.apache.solr.core.CoreContainer.getZkController()" is null
at
org.apache.solr.handler.admin.proxy.RemoteRequestProxy.validateNodeNames(RemoteRequestProxy.java:154)
at
org.apache.solr.handler.admin.proxy.GenericV1RequestProxy.getDestinationNodes(GenericV1RequestProxy.java:55)
at
org.apache.solr.handler.admin.proxy.RemoteRequestProxy.proxyRequest(RemoteRequestProxy.java:86)
at
org.apache.solr.handler.admin.LoggingHandler.handleRequestBody(LoggingHandler.java:95)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:251)
at
org.apache.solr.handler.admin.InfoHandler.handle(InfoHandler.java:109)
at
org.apache.solr.handler.admin.InfoHandler.handleRequestBody(InfoHandler.java:97)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:251)
at
org.apache.solr.servlet.HttpSolrCall.handleAdmin(HttpSolrCall.java:747)
at
org.apache.solr.servlet.HttpSolrCall.handleAdminRequest(HttpSolrCall.java:706)
at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:473)
{noformat}
> standalone solr 10 logging UI tries to access zookeeper: NullPointerException
> -----------------------------------------------------------------------------
>
> Key: SOLR-18317
> URL: https://issues.apache.org/jira/browse/SOLR-18317
> Project: Solr
> Issue Type: Test
> Affects Versions: 10.0
> Reporter: Chris M. Hostetter
> Priority: Major
>
> The following problem affects solr-10 and the current 10x branch (but with
> slightly different stack traces)
> When using solr in "user managed" (aka: standalone) mode, attempts to use the
> admin UI logging screen to change the log level succeed in changing the log
> level on the node, but also cause a NullPointerException as the underlying
> java code tries to use zookeeper to lookup a list of nodes to proxy the
> request to.
> Making an explicit request to {{/admin/info/logging?set=...}} does not cause
> a NullPointerException.
> The underlying problem seems to be a disconnect in the
> assumptions/preconditions in various pieces of code:
> * the UI assumes it can _*always*_ include the {{nodes=all}} param when
> sending {{set=...}} to {{/admin/info/logging}}
> * {{AdminHandlersProxy.resolveNodes()}} and/or
> {{RemoteRequestProxy.validateNodeNames()}} seem to assume they will only be
> invoked in a "cloud" deployment
> * callers to {{AdminHandlersProxy.resolveNodes()}} and/or
> {{RemoteRequestProxy.validateNodeNames()}} seem to assume requests should be
> proxied anytime a {{node(s)}} param is specified.
> {panel}I believe this bug affects any Solr APIs that may delegate to
> {{AdminHandlersProxy}} and/or {{RemoteRequestProxy}} -- so at a minimum that
> would be {{LoggingHandler}}, {{MetricsHandler}}, and {{SystemInfoHandler}}
> {panel}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
