[
https://issues.apache.org/jira/browse/SOLR-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651360#comment-15651360
]
Elaine Cario commented on SOLR-7951:
------------------------------------
We've upgraded now to Solr 5.5.2 (unpatched) and users are now reporting this
issue again in the same scenario - use of wildcard in the query reports too
many expansions, every shard reports the same exception, and instead of the
actual exception, we get the "No live servers...." exception.
I suppose we can run again with a locally patched Solr, but it would be really
nice to have this fixed in Solr 6.x.
Thanks.
> 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
> Assignee: Mark Miller
> Priority: Minor
> Attachments: SOLR-7951-4.x.patch, SOLR-7951-4.x.patch, 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
