[
https://issues.apache.org/jira/browse/SOLR-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368718#comment-14368718
]
Luc Vanlerberghe commented on SOLR-7273:
----------------------------------------
I forgot to mention that I would only include this for the search handlers to
allow applications to continue in a reduced functionality state instead of not
replying or being forced to show an error box.
In the case I encountered, the hightlight component threw an exception in very
specific cases (certain documents being present in the result page for certain
queries). 99% of the time it worked just fine. I have determined the cause,
but have no quick solution yet so swtiches like these would at least keep the
application running (without highlights for those documents)
It's no use (and probably dangerous) for update handlers to try to work around
exceptions...
> Add "tolerant" switches to configure behaviour when a component throws an
> exception
> -----------------------------------------------------------------------------------
>
> Key: SOLR-7273
> URL: https://issues.apache.org/jira/browse/SOLR-7273
> Project: Solr
> Issue Type: Improvement
> Components: SearchComponents - other
> Reporter: Luc Vanlerberghe
> Priority: Minor
>
> Was: "An Exception in a non-query component should not cause a global HTTP
> 500 Server Error response" on the dev list.
> The current behavior of Solr on any component throwing an error is to send a
> response containing the results of the components that did succeed with a
> HTTP status code of 500 Server Error.
> I propose to implement switches similar to the "shards.tolerant" ones that
> would allow Solr to return the response without the 500 HTTP status.
> A global switch might be useful to ask Solr to return only the 500 HTTP
> status and the exception details without the rest of the response, but
> otherwise I believe the switches should be per component since only at that
> level can be decided what the impact might be.
> E.g. for the highlight component, the switch could be
> "component.highlight.tolerant=true" to cause it to ignore (but still log!)
> InvalidTokenOffsetsExceptions and either return the rest of the results or
> return no results at all.
> The response format could be extended too to allow more than one exception to
> be included (per component or simply a list?) without necessarily changing
> the HTTP status to 500.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
