[
https://issues.apache.org/jira/browse/SOLR-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000782#comment-15000782
]
Elaine Cario commented on SOLR-7951:
------------------------------------
NP - we applied patch to 4.10 in our prod environment some weeks ago, so far
have seen no issues (and it fixed the issue we were having). But it would be
good to get it in 5.x so I don't need to worry about carrying the patch forward
when we upgrade (no date for that, but it's in the planning stages).
Thanks for the follow-up!
> 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
