[
https://issues.apache.org/jira/browse/SOLR-12005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421358#comment-16421358
]
Shawn Heisey commented on SOLR-12005:
-------------------------------------
[~janhoy], I think that some things previously logged at info were not
excessive. In this case, it's a bunch of extra lines, but only at startup (or
reload). I do understand the goal of reducing logging verbosity, so I'm not
going to insist. I wonder if maybe we can log all the jar names loaded from
one directory or one config entry on one line. It's too bad that "less"
doesn't truncate long lines by default.
For service installs, the "-v" startup option is usually not available, but it
does look like setting SOLR_LOG_LEVEL=DEBUG in solr.in.sh might do the same
thing. And it is mentioned in solr.in.sh. Therefore, I know how to ask a user
to turn on the more verbose logging, and turn it back off when the info is
gathered.
+1 to utilizing TRACE more. Also, WARN should *maybe* have more in it. There
are certain major events, technically are not warnings, that I think *should*
be visible even when somebody sets their level to WARN. I'm aware of the
contradiction of using WARN for things that are normal and not cause for
concern.
Historically, WARN was a famine, INFO was a feast, and DEBUG was insane. Now,
WARN hasn't really changed, INFO is getting better, and DEBUG is still insane.
> 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]
