lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Ribeiro (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-7951) LBHttpSolrClient wraps ALL exceptions in "No live SolrServers available to handle this request" exception, even usage errors
Date Thu, 20 Aug 2015 20:18:46 GMT

     [ https://issues.apache.org/jira/browse/SOLR-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Edward Ribeiro updated SOLR-7951:
---------------------------------
    Attachment: SOLR-7951.patch

Hi [~markrmiller@gmail.com] and [~ecario], I am attaching a patch for your evaluation. It's
just a suggestion so feel free to ignore it or improve on it. :) 

Mark, while looking at this issue, I have seen that LBHttpSolrClientTest (with only a test
method) and TestLBHttpSolrClient. Maybe it would be a nice opportunity to merge them? Furthermore,
I have included a simple test into TestLBHttpSolrClient, but I am not quite pleased with it.
Wdyt? 

If you could suggest a better way of testing this issue, it would be really nice, but otherwise
we can keep it as-is, or remove it.

> LBHttpSolrClient wraps ALL exceptions in "No live SolrServers available to handle this
request" exception, even usage errors
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-7951
>                 URL: https://issues.apache.org/jira/browse/SOLR-7951
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrJ
>    Affects Versions: 5.2.1
>            Reporter: Elaine Cario
>            Priority: Minor
>         Attachments: SOLR-7951.patch
>
>
> We were experiencing many "No live SolrServers available to handle this request" exception,
even though we saw no outages with any of our servers.  
> It turned out the actual exceptions were related to the use of wildcards in span queries
(and in some cases other invalid queries or usage-type issues). Traced it back to LBHttpSolrClient
which was wrapping all exceptions, even plain SolrExceptions, in that outer exception.  
> Instead, wrapping in the out exception should be reserved for true communication issues
in SolrCloud, and usage exceptions should be thrown as is.



--
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


Mime
View raw message