[jira] [Commented] (SOLR-7381) Improve Debuggability of SolrCloud using MDC

["Ted Yu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671925#comment-16671925 ] 

Ted Yu commented on SOLR-7381:
------------------------------

I was looking at MDCAwareFixedThreadPool and found this JIRA.

I wonder if what was stated here is relevant:
http://ashtonkemerling.com/blog/2017/09/01/mdc-and-threadpools/

Thanks

> Improve Debuggability of SolrCloud using MDC
> --------------------------------------------
>
>                 Key: SOLR-7381
>                 URL: https://issues.apache.org/jira/browse/SOLR-7381
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Shalin Shekhar Mangar
>            Priority: Critical
>             Fix For: 5.2, 6.0
>
>         Attachments: SOLR-7381-forbid-threadpoolexecutor.patch, SOLR-7381-submitter-stacktrace.patch, SOLR-7381-thread-names.patch, SOLR-7381-thread-names.patch, SOLR-7381-thread-names.patch, SOLR-7381.patch, SOLR-7381.patch
>
>
> SOLR-6673 added MDC based logging in a few places but we have a lot of ground to cover.
> # Threads created via thread pool executors do not inherit MDC values and those are some of the most interesting places to log MDC context.
> # We must expose node names (in tests) so that we can debug faster
> # We can expose more information via thread names so that a thread dump has enough context to help debug problems in production
> This is critical to help debug SolrCloud failures.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org