[
https://issues.apache.org/jira/browse/SOLR-6673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381828#comment-14381828
]
Varun Thacker commented on SOLR-6673:
-------------------------------------
bq. 34093 T174 C:collection1 S:shard1 R:core_node6 c:collection1 C17 P62757
oasup.LogUpdateProcessor.finish [collection1] webapp=/ar path=/update
params={update.distrib=FROMLEADER&distrib.from=http://127.0.0.1:62746/ar/collection1/&wt=javabin&version=2}
{add=[100000478 (1496644420418666496), 100000479 (1496644420419715072)]} 0 1
Can we be more verbose about it? Call 'C' 'Collection' and 'c' 'core'?
{{981970 T4850 C:collection1 c:collection1 oasc.ZkController.watchZKConfDir
watch zkdir /configs/conf1}}
Lines like this could confuse someone.
Don't have a strong opinion about it though.
> 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
