[
https://issues.apache.org/jira/browse/SOLR-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069029#comment-15069029
]
Shawn Heisey commented on SOLR-8248:
------------------------------------
bq. Is there a reason Solr doesn't use log4j2 or logback as these are supposed
to faster than log4j
Boring TL;DR history:
For most of its history, Solr has been using slf4j logging (from slf4j.org),
bound to java.util.logging.
In version 4.3, logging jars were removed from the war file, moved to jetty's
lib/ext folder, and the binding was changed to log4j 1.2. I do not know why
the older log4j was chosen, perhaps it was simply a familiar library.
Speculation says that part of it may have come from loyalty to a fellow Apache
project, and the fact that the library on slf4j.org does not support log4j2.
Just this year, log4j 1.x was declared completely end of life, so we have an
issue to upgrade the binding to log4j2 (still using slf4j within Solr), but
this is not a simple drop-in replacement. Code changes will likely be required
to keep the Logging tab in the admin UI working. Jar changes will also be
required.
> Log a query as soon as it comes in and assign a unique id to it
> ---------------------------------------------------------------
>
> Key: SOLR-8248
> URL: https://issues.apache.org/jira/browse/SOLR-8248
> Project: Solr
> Issue Type: Improvement
> Components: Server
> Affects Versions: 5.3
> Reporter: Pushkar Raste
> Priority: Minor
>
> Often times when there is an OutOfMemory error Solr fails to log details
> about query that might have caused it. Solr doesn't provide enough
> information to investigate the root cause in such case.
> We can log a query as soon as it comes in and reference it by it's unique id
> to log details like Hits, Status and QTime when query finishes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
