You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2021/02/25 20:40:00 UTC
[jira] [Commented] (SOLR-15198) Slf4j logs threadName incorrectly
in some cases
[ https://issues.apache.org/jira/browse/SOLR-15198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291205#comment-17291205 ]
David Smiley commented on SOLR-15198:
-------------------------------------
From the title, if the problem is indeed in Slf4j then report it there. But, based on a previous discussion we had, my understanding of the problem is that the thread names are unreasonably long.
Tip: If you want to put raw info into JIRA, use JIRA's syntax, not GitHub. As I write this in the rich text editor, there's a "+" icon in the toolbar with a "preformatted" option. That is ultimately a simple pair of tags \{noformat\}.
> Slf4j logs threadName incorrectly in some cases
> -----------------------------------------------
>
> Key: SOLR-15198
> URL: https://issues.apache.org/jira/browse/SOLR-15198
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: logging
> Affects Versions: 8.6
> Reporter: Megan Carey
> Priority: Minor
>
> I'm running Solr 8.6, and I'm seeing some logs report threadName with the entire log message and MDC. I haven't dug in too much, but CoreContainer logs seem to be the biggest culprit. Not sure if it's an issue of thread naming (including delimiter in name?), SolrLogFormat parsing, or something else altogether.
> ```
> { [
> CoreAdminHandler.action: CREATE
> CoreAdminHandler.asyncId: rebalance_replicas_trigger/41b16883a3bcTdzc5xqm9leudgekft79dpj5zl/372246269149506
> collection: collectionName
> core: collectionName_shard1_0_0_0_1_0_0_0_1_1_0_1_0_0_replica_s7606
> level: INFO
> logger: org.apache.solr.core.CoreContainer
> message: Creating SolrCore 'collectionName_shard1_0_0_0_1_0_0_0_1_1_0_1_0_0_replica_s7606' using configuration from configset crm, trusted=true
> node_name: seas-solr-8.solr.prod1-eks-use1-seas-1.svc.cluster.local:8983_solr
> replica: core_node7607
> shard: shard1_0_0_0_1_0_0_0_1_1_0_1_0_0
> threadId: 4861
> *threadName: parallelCoreAdminExecutor-19-thread-6-processing-n:seas-solr-8.solr.prod1-eks-use1-seas-1.svc.cluster.local:8983_solr x:collectionName_shard1_0_0_0_1_0_0_0_1_1_0_1_0_0_replica_s7606 t:Shared-932ac44c-06a4-44d3-ba8f-5a64c8f8d708 rebalance_replicas_trigger//41b16883a3bcTdzc5xqm9leudgekft79dpj5zl//372246269149506 CREATE*
> timestamp: 2021-02-03T16:26:56.482Z
> trace_id: Shared-932ac44c-06a4-44d3-ba8f-5a64c8f8d708
> }
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org