[
https://issues.apache.org/jira/browse/SOLR-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137444#comment-15137444
]
Shawn Heisey commented on SOLR-6919:
------------------------------------
I was really confused when I was looking at my Solr 5 logs, because the class
being logged on every request was not a class that I could find. I finally
figured out why -- the "class" only exists as a logger instance on SolrCore.
Do we want to have logs coming from a class that doesn't exist? This might be
perfectly OK, but it did lead me on a bit of a snipe hunt.
> Log REST info before executing
> ------------------------------
>
> Key: SOLR-6919
> URL: https://issues.apache.org/jira/browse/SOLR-6919
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Mike Drob
> Assignee: Gregory Chanan
> Priority: Minor
> Fix For: 5.1, Trunk
>
> Attachments: SOLR-6919.patch, SOLR-6919.patch, SOLR-6919.patch,
> SOLR-6919.patch, SOLR-6919.patch, SOLR-6919.patch
>
>
> We should log request info (path, parameters, etc...) before attempting to
> execute a query. This is helpful in cases where we get a bad query that
> causes OOM or something else catastrophic, and are doing post-event triage.
--
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
