[
https://issues.apache.org/jira/browse/SOLR-15011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17279090#comment-17279090
]
Chris M. Hostetter commented on SOLR-15011:
-------------------------------------------
also: to prevent future debuggign headaches, please change this pattern...
{code}
try {
rsp = solrClient.query("collection", mparams, SolrRequest.METHOD.GET);
} catch (Exception e) {
fail("Exception while proxying request to node " + node);
}
{code}
...to something like this, so the details of how/why/what failed are included...
{code}
try {
rsp = solrClient.query("collection", mparams, SolrRequest.METHOD.GET);
} catch (Exception e) {
throw new AssertionFailure("Exception while proxying request to node "
+ node, e);
}
{code}
> /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
