[
https://issues.apache.org/jira/browse/SOLR-14998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17233121#comment-17233121
]
ASF subversion and git services commented on SOLR-14998:
--------------------------------------------------------
Commit 4d904e523c9bc36f36403b9f3831b0563f3a1f79 in lucene-solr's branch
refs/heads/branch_8x from Nazerke Seidan
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=4d904e5 ]
SOLR-14998: logging: info->debug in CollectionsHandler (#2079)
Because it's almost always redundant with HttpSolrCall's admin request log.
Co-authored-by: Nazerke Seidan <nsei...@salesforce.com>
(cherry picked from commit 2d583eaba7ab8eb778bebbc5557bae29ea481830)
> any Collections Handler actions should be logged at debug level
> ---------------------------------------------------------------
>
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
