[
https://issues.apache.org/jira/browse/SOLR-15136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283521#comment-17283521
]
Noble Paul commented on SOLR-15136:
-----------------------------------
LGTM
> need to audit for excesive INFO level logging after SOLR-15052
> --------------------------------------------------------------
>
> Key: SOLR-15136
> URL: https://issues.apache.org/jira/browse/SOLR-15136
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Assignee: Ishan Chattopadhyaya
> Priority: Major
> Attachments: SOLR-15136.patch
>
>
> Markus Jelsma noted on solr-user thread that 8.8 introduced an excessive
> amount of INFO level logging, notable from ZkStateReader...
> http://mail-archives.apache.org/mod_mbox/lucene-solr-user/202102.mbox/%3CCAJvgyxqDBNjPtzamszOf1ZZiZGPg42PYegYbHPkVMm5OF1%3DaVw%40mail.gmail.com%3E
> this appears to be caused by SOLR-15052, but is not consistent between master
> and branch_8x. at a glance it appears there was lots of new logging
> introduced originally at the INFO level with "nocommit" comments to dial down
> to debug -- some of which happened, but evidently a lot didn't
> I'm filing this issue in the hopes that the folks involved in SOLR-15052 will
> please go back and do a thorough review of what logging is on master vs 8x
> and carefully reconsider what log messages added for development purposes are
> still useful, and what levels they should be at.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]