[
https://issues.apache.org/jira/browse/SOLR-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493687#comment-14493687
]
ASF subversion and git services commented on SOLR-7381:
-------------------------------------------------------
Commit 1673373 from sha...@apache.org in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1673373 ]
SOLR-7381: Usages of Executors#newFixedThreadPool, #newSingleThreadExecutor,
#newCachedThreadPool as well as ThreadPoolExecutor directly is now forbidden in
Solr
> 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
>
> Attachments: SOLR-7381-forbid-threadpoolexecutor.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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
