Lyle created SOLR-14317:
---------------------------

             Summary: HttpClusterStateProvider throws exception when only one 
node down
                 Key: SOLR-14317
                 URL: https://issues.apache.org/jira/browse/SOLR-14317
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
          Components: SolrJ
    Affects Versions: 7.7.2, 7.7.1
            Reporter: Lyle


When create a CloudSolrClient with solrUrls, if the first url in the solrUrls 
list is invalid or server is down, it will throw exception directly rather than 
try remaining url.

In 
[https://github.com/apache/lucene-solr/blob/branch_7_7/solr/solrj/src/java/org/apache/solr/client/solrj/impl/HttpClusterStateProvider.java#L65],
 if fetchLiveNodes(initialClient) have any IOException, in 
[https://github.com/apache/lucene-solr/blob/branch_7_7/solr/solrj/src/java/org/apache/solr/client/solrj/impl/HttpSolrClient.java#L648],
 exceptions will be caught and throw SolrServerException to the upper caller, 
while no IOExceptioin will be caught in 
HttpClusterStateProvider.fetchLiveNodes(HttpClusterStateProvider.java:200).

The SolrServerException should be caught as well in 
[https://github.com/apache/lucene-solr/blob/branch_7_7/solr/solrj/src/java/org/apache/solr/client/solrj/impl/HttpClusterStateProvider.java#L69],
 so that if first node provided in solrUrs down, we can try to use the second 
to fetch live nodes.

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to