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 2020/11/13 16:42:00 UTC
[jira] [Commented] (SOLR-14998) CLUSTERSTATUS info level logging
is redundant in CollectionsHandler
[ https://issues.apache.org/jira/browse/SOLR-14998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231618#comment-17231618 ]
David Smiley commented on SOLR-14998:
-------------------------------------
So it's super-clear, can you comment an example of what both logs look like? Is this specific to CLUSTERSTATUS (you put it in the title) or is it *any* Collections handler actions?
> CLUSTERSTATUS info level logging is redundant in CollectionsHandler
> ---------------------------------------------------------------------
>
> Key: SOLR-14998
> URL: https://issues.apache.org/jira/browse/SOLR-14998
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Nazerke Seidan
> Priority: Minor
>
> CLUSTERSTATUS is logged in CollectionsHandler at INFO level but the cluster status is already logged in HttpSolrCall at INFO. In CollectionsHandler INFO level should be set to DEBUG to avoid a lot of noise.
--
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