Hoss Man created SOLR-13792:
-------------------------------
Summary: SolrZkClient should include more MDC info when zkCallback
threads process a WatchedEvent
Key: SOLR-13792
URL: https://issues.apache.org/jira/browse/SOLR-13792
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Hoss Man
One of the biggest headaches when debigging multi-node cloud tests is
disambiguiating the log messages and what nodes they came from.
For many threads, the MDC context info makes this a non-issue, but in the case
of "zkCallback" threads it can be virtually impossible to tell which "node" of
the cluster each of the zkCallback threads belongs to, because they don't have
MDC info ({{SolrZkClient}} already uses an {{MDCAwareThreadPoolExecutor}} to
process the ZK {{WatchEvent}} callbacks, and {{MDCAwareThreadPoolExecutor}}
ensures that the _submitter's_ MDC values are used in the Thread that executes
the Runnable -- but in this case the "submitter" is the ZooKeeper Thread.
>From a test debugging standpoint, it would be very useful if more MDC context
>info about the *node* existed when {{zkCallback}} thread's execute.
--
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
