[ 
https://issues.apache.org/jira/browse/SOLR-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069907#comment-15069907
 ] 

Shawn Heisey commented on SOLR-8248:
------------------------------------

SOLR-7887 is the issue to upgrade log4j.  Feel free to join in there.

> 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

Reply via email to