You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jason Gerlowski (JIRA)" <ji...@apache.org> on 2015/11/07 21:33:10 UTC
[jira] [Commented] (SOLR-8248) Log a query as soon as it comes in
and assign a unique id to it
[ https://issues.apache.org/jira/browse/SOLR-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995400#comment-14995400 ]
Jason Gerlowski commented on SOLR-8248:
---------------------------------------
>From a novice's perspective, this seems like a useful improvement, +1. Though maybe there's performance-issues, or other things preventing this that I don't know about.
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org