[
https://issues.apache.org/jira/browse/SOLR-6673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381847#comment-14381847
]
Yonik Seeley commented on SOLR-6673:
------------------------------------
bq. Can we be more verbose about it? Call 'C' 'Collection' and 'c' 'core'?
If this stuff will be repeated in every log line, I like the fact that it's
short, and that should actually enhance readability once you get used to it.
There is some other redundant info now though: C17 P62757
That's the core number and the port number. Both where important in the past
(along with the thread number) to figuring out chaos monkey test fails. But
they don't seem important for production? The port number should be different
for diff log files in production, and the collection name we already have.
> MDC based logging of collection, shard etc.
> -------------------------------------------
>
> Key: SOLR-6673
> URL: https://issues.apache.org/jira/browse/SOLR-6673
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Assignee: Noble Paul
> Labels: logging
> Fix For: Trunk, 5.1
>
> Attachments: SOLR-6673-log-more.patch, SOLR-6673.patch,
> SOLR-6673.patch, SOLR-6673.patch, SOLR-6673.patch, SOLR-6673.patch,
> SOLR-6673.patch, SOLR-6673.patch, SOLR-6673.patch, log4j.properties,
> log4j.properties
>
>
> In cloud mode, the many log items don't contain the collection name, shard
> name, core name etc. Debugging becomes specially difficult when many
> collections/shards are hosted on the same node.
> The proposed solution adds MDC based stamping of collection, shard, core to
> the thread.
> See also: SOLR-5969, SOLR-5277
--
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
