[
https://issues.apache.org/jira/browse/SOLR-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068898#comment-15068898
]
Pushkar Raste commented on SOLR-8248:
-------------------------------------
[SOLR-6919|https://issues.apache.org/jira/browse/SOLR-6919] logs REST request,
however request may get modified based on the solr config.
[~yo...@apache.org] I do agree that correlating query would be a problem
(especially in multi sharded envirnment), other alternative is to log query
twice and control logging query the first time if a flag is turned on. This
however would also increase disk footprint of log files a lot.
Is there a reason Solr doesn't use log4j2 or logback as these are supposed to
faster than log4j
> 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
