[
https://issues.apache.org/jira/browse/SOLR-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123429#comment-18123429
]
ASF subversion and git services commented on SOLR-18317:
--------------------------------------------------------
Commit ca0ad8281f6ddd4d1943a0028487f0bd287144f6 in solr's branch
refs/heads/branch_10x from Nick
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=ca0ad8281f6 ]
SOLR-18317: Admin UI no longer sends nodes=all in standalone mode (#5001)
Co-authored-by: Eric Pugh <[email protected]>
(cherry picked from commit e432df19c4a50b9d54d7fba545397b859cc54f98)
> 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: Blocker
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> 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]
