[
https://issues.apache.org/jira/browse/SOLR-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated SOLR-6919:
----------------------------
Attachment: SOLR-6919.patch
bq. should the slow query log also go to the request log?
I can see an argument made for this, but I don't think it is necessary.
bq. if you are generating this on top of what is already committed why does the
test case look like a new file?
I'm not sure, I must have made a mistake somewhere. Here's a new patch that
looks correct w.r.t. the test case.
> 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: Trunk, 5.1
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
