[
https://issues.apache.org/jira/browse/SOLR-14351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075007#comment-17075007
]
ASF subversion and git services commented on SOLR-14351:
--------------------------------------------------------
Commit 1aeefc25d1ae5e1a56cce333f57c6f044da372de in lucene-solr's branch
refs/heads/master from David Smiley
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=1aeefc2 ]
SOLR-14351: Fix/improve MDCLoggingContext usage
* Some set/clear were not balanced.
* Harden clear() in case of imbalance.
* Sometimes coreContainger.getCore was called unnecessarily; just need a
descriptor
* SolrCore.open/close now calls MDCLoggerContext.setCore/clear
* no need to clear MDC in HttpSolrCall
> Harden MDCLoggingContext.clear depth tracking
> ---------------------------------------------
>
> Key: SOLR-14351
> URL: https://issues.apache.org/jira/browse/SOLR-14351
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> MDCLoggingContext tracks recursive calls and only clears when the recursion
> level is back down to 0. If a caller forgets to register and ends up calling
> clear any ways, then this can mess things up. Additionally I found at least
> one place this is occurring, which led me to investigate this matter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
