[
https://issues.apache.org/jira/browse/SOLR-12005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421360#comment-16421360
]
Shawn Heisey commented on SOLR-12005:
-------------------------------------
Further drifting into "needs a new issue" territory:
An example of something that I think should be at WARN, even though it's 100%
normal and no cause for concern: The point where Solr startup is complete --
all cores are loaded or inventoried, cloud information cached, background
threads started, etc. And maybe that log line should have an elapsed time from
webapp startup. Getting it from Jetty startup might not be possible, but if
Jetty exposes that information, let's log that too.
> Solr should have the option of logging all jars loaded
> ------------------------------------------------------
>
> Key: SOLR-12005
> URL: https://issues.apache.org/jira/browse/SOLR-12005
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: logging
> Reporter: Shawn Heisey
> Priority: Major
>
> Solr used to explicitly log the filename of every jar it loaded. It seems
> that the effort to reduce the verbosity of the logs has changed this, now it
> just logs the *count* of jars loaded and the paths where they were loaded
> from. Here's a log line where Solr is reading from ${solr.solr.home}/lib:
> {code}
> 2018-02-01 17:43:20.043 INFO (main) [ ] o.a.s.c.SolrResourceLoader [null]
> Added 8 libs to classloader, from paths: [/index/solr6/data/lib]
> {code}
> When trying to help somebody with classloader issues, it's more difficult to
> help when the list of jars loaded isn't in the log.
> I would like the more verbose logging to be enabled by default, but I
> understand that many people would not want that, so I propose this:
> * Enable verbose logging for ${solr.solr.home}/lib by default.
> * Disable verbose logging for each core by default. Allow solrconfig.xml to
> enable it.
> * Optionally allow solr.xml to configure verbose logging at the global level.
> ** This setting would affect both global and per-core jar loading. Each
> solrconfig.xml could override.
> Rationale: The contents of ${solr.solr.home}/lib are loaded precisely once,
> and this location doesn't even exist unless a user creates it. An
> out-of-the-box config would not have verbose logs from jar loading.
> The solr home lib location is my preferred way of loading custom jars,
> because they get loaded only once, no matter how many cores you have. Jars
> added to this location would add lines to the log, but it would not be logged
> for every core.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
