Chris M. Hostetter created SOLR-18317:
-----------------------------------------
Summary: 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
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]
