[jira] [Reopened] (SOLR-15011) /admin/logging handler should be able to configure logs on all nodes

["Chris M. Hostetter (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-15011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris M. Hostetter reopened SOLR-15011:
---------------------------------------
      Assignee: David Smiley

The newly added test has been failing all sorts of apache jenkins builds, with various seeds, since it was committed...

{noformat}
FAILED:  org.apache.solr.handler.admin.AdminHandlersProxyTest.proxyLoggingHandlerAllNodes

Error Message:
java.lang.AssertionError: expected:<WARN> but was:<null>

Stack Trace:
java.lang.AssertionError: expected:<WARN> but was:<null>
        at __randomizedtesting.SeedInfo.seed([C78B0D19C017E212:CAD2CB534253078E]:0)
        at org.junit.Assert.fail(Assert.java:89)
        at org.junit.Assert.failNotEquals(Assert.java:835)
        at org.junit.Assert.assertEquals(Assert.java:120)
        at org.junit.Assert.assertEquals(Assert.java:146)
        at
org.apache.solr.handler.admin.AdminHandlersProxyTest.lambda$proxyLoggingHandlerAllNodes$0(AdminHandlersProxyTest.jav
a:122)
        at java.base/java.lang.Iterable.forEach(Iterable.java:75)
        at
org.apache.solr.handler.admin.AdminHandlersProxyTest.proxyLoggingHandlerAllNodes(AdminHandlersProxyTest.java:111)

{noformat}

> /admin/logging handler should be able to configure logs on all nodes
> --------------------------------------------------------------------
>
>                 Key: SOLR-15011
>                 URL: https://issues.apache.org/jira/browse/SOLR-15011
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: logging
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Major
>             Fix For: master (9.0)
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> The LoggingHandler registered at /admin/logging can configure log levels for the current node.  This is nice but in SolrCloud, what's needed is an ability to change the level for _all_ nodes in the cluster.  I propose that this be a parameter name "distrib" defaulting to SolrCloud mode's status.  An admin UI could have a checkbox for it.  I don't propose that the read operations be changed -- they can continue to just look at the node you are hitting.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org