[
https://issues.apache.org/jira/browse/SOLR-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069873#comment-15069873
]
Pushkar Raste commented on SOLR-8248:
-------------------------------------
slfj and log4j2 do well go together, check this out
[https://logging.apache.org/log4j/2.0/log4j-slf4j-impl/index.html]
and log4j2 too is a apache project, so we still would be loyal to apache
foundation :-)
Here is an article that compares log4j, logback and log4j2
I understand that there will be lot of work involved in moving to log4j2 but
that would be justified given that it has significant performance benefits over
log4j and and the fact that log4j 1.x is resting in peace
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
