[
https://issues.apache.org/jira/browse/SOLR-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763488#comment-17763488
]
ASF subversion and git services commented on SOLR-16044:
--------------------------------------------------------
Commit 5d2d59a9bd9393dfa85ea108338bef3f5df45213 in solr's branch
refs/heads/branch_9x from Jan Høydahl
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=5d2d59a9bd9 ]
SOLR-16044: SlowRequest logging disabled if SolrCore logger set to ERROR (#1907)
(cherry picked from commit ca4692b5a26a060831a6682e4961f93b9871362b)
> SlowRequest logging disabled if SolrCore logger set to ERROR
> ------------------------------------------------------------
>
> Key: SOLR-16044
> URL: https://issues.apache.org/jira/browse/SOLR-16044
> Project: Solr
> Issue Type: Bug
> Components: logging
> Environment: Solr 8.4
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If someone sets ROOT logger to ERROR, then {{SolrCore}} class will also be
> set to ERROR, and even if {{SolrCore.SlowRequest}} level is set to INFO, no
> logs will be written to {{{}solr_slow_requests.log{}}}.
> Some debugging revealed that changing log level of {{SolrCore}} to WARN fixes
> it. This suggests that since {{SlowRequest}} is not a real class but just a
> logger name, it is still subject to the log level of {{SolrCore}}.
> I suppose that the same will be true for {{SolrCore.Request}} logging.
> One solution could be to create a real class for SlowRequest logging. Another
> solution could be to explicitly set {{SolrCore}} level in {{log4j2.xml}} so
> that it does not follow the ROOT level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
