[ https://issues.apache.org/jira/browse/SOLR-14351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106763#comment-17106763 ]
ASF subversion and git services commented on SOLR-14351: -------------------------------------------------------- Commit f00b38d004831512de21ed1f8289b2e939dafbd3 in lucene-solr's branch refs/heads/branch_8x from David Smiley [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=f00b38d ] SOLR-14351: commitScheduler was missing MDC logging (#1498) (cherry picked from commit 4b9808a03d6c8ee1f1f71487372a689b6c5f9798) > 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 > Fix For: 8.6 > > Time Spent: 1h 40m > 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: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org