[
https://issues.apache.org/jira/browse/SOLR-15011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282092#comment-17282092
]
Chris M. Hostetter commented on SOLR-15011:
-------------------------------------------
BadApple'ing the test just prevents it from being a noisy failure on jenkins
... BadApple tests are still run on developer boxes by default, so this test is
still causing lots of failures.
{quote}I tried something else that occurred to me... I merely commented out the
substance of the issue (LoggingHandler calling into AdminHandlersProxy) and...
the test still passed. I'm not surprised; this is an embedded test and thus all
nodes share the same logging state. Hmm. I wonder if we can't realistically
test this until we have Docker based test infrastructure with fully isolated
Solr nodes.
{quote}
If that's the case then i would suggest the test just be deleted – or
explicitly @AwaitsFixed – but if it's going to stick around in a disabled state
it should probably point at a new Jira to track if/how/when we might be able to
adequately test it, so that the current Jira can be re-resolved and correctly
track when this functionality was added.
> /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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
