[ 
https://issues.apache.org/jira/browse/SOLR-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743775#action_12743775
 ] 

Lance Norskog commented on SOLR-1143:
-------------------------------------

If the search subsystem has a problem, the ops team wants to know about it and 
fix it. This just hides problems.

An example: 2 servers with the same shard are behind a load balancer. One 
server fails. The load balancer notices this and directs all traffic to the 
other server.

This is a production network which serves and outside API, where everything is 
supposed to work >from the viewpoint of the outside API<. When the load 
balancer gets a failure it usually returns an error on that one request, then 
marks the server down. So that one search request eventually returns with a 
"temporary error" condition.

These search requests come from an app server which serves the API. The app 
server then has the option of retrying one or two times, or returning "service 
not happy" to the outside calling app.

When I have a problem in my system, I want to find it and fix it.  Ignoring 
shard errors is ok as an option, and should be there. But, please do not make 
it the default.  Hiding failures should never be the default.

> Return partial results when a connection to a shard is refused
> --------------------------------------------------------------
>
>                 Key: SOLR-1143
>                 URL: https://issues.apache.org/jira/browse/SOLR-1143
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>            Reporter: Nicolas Dessaigne
>             Fix For: 1.4
>
>         Attachments: SOLR-1143.patch
>
>
> If any shard is down in a distributed search, a ConnectException it thrown.
> Here's a little patch that change this behaviour: if we can't connect to a 
> shard (ConnectException), we get partial results from the active shards. As 
> for TimeOut parameter (https://issues.apache.org/jira/browse/SOLR-502), we 
> set the parameter "partialResults" at true.
> This patch also adresses a problem expressed in the mailing list about a year 
> ago 
> (http://www.nabble.com/partialResults,-distributed-search---SOLR-502-td19002610.html)
> We have a use case that needs this behaviour and we would like to know your 
> thougths about such a behaviour? Should it be the default behaviour for 
> distributed search?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to