You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (Commented) (JIRA)" <ji...@apache.org> on 2012/02/23 23:19:50 UTC
[jira] [Commented] (SOLR-3129) Move a lot of the startup logging to
trace.
[ https://issues.apache.org/jira/browse/SOLR-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215119#comment-13215119 ]
Mark Miller commented on SOLR-3129:
-----------------------------------
Hmm..thought I had provided a patch. I intend to do this if no one objects. I tried it out a while back, and reading the more pertinent startup info becomes much easier.
> Move a lot of the startup logging to trace.
> -------------------------------------------
>
> Key: SOLR-3129
> URL: https://issues.apache.org/jira/browse/SOLR-3129
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 4.0
>
>
> We should make the start up logging cleaner - 9 times out of 10 you don't need all that info and 9 times out of 10 it just makes it harder to find what you do need - especially if you have a lot of core reloads.
> I think most of the "added" and "created" events can go to trace - when you need that info you can easily broaden the log level - but for the majority case when you don't, lets clean this up?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org