[jira] [Updated] (SOLR-4044) CloudSolrServer early connect problems

["Alan Woodward (JIRA)" <ji...@apache.org>]

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

Alan Woodward updated SOLR-4044:
--------------------------------
    Attachment: SOLR-4044-waitforcluster.patch

bq. Can we overload connect with a boolean waitForCluster and timeout parameters instead?

Yes, that's nicer.  No need for the boolean as the presence of timeout parameters implies that you're ready to wait.  Here's a patch.

> CloudSolrServer early connect problems
> --------------------------------------
>
>                 Key: SOLR-4044
>                 URL: https://issues.apache.org/jira/browse/SOLR-4044
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.0
>            Reporter: Grant Ingersoll
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: 4.9, Trunk
>
>         Attachments: SOLR-4044-waitforcluster.patch, SOLR-4044-waitforcluster.patch, SOLR-4044-waitforcluster.patch, SOLR-4044.patch
>
>
> If you call CloudSolrServer.connect() after Zookeeper is up, but before clusterstate, etc. is populated, you will get "No live SolrServer" exceptions (line 322 in LBHttpSolrServer):
> {code}
> throw new SolrServerException("No live SolrServers available to handle this request");{code}
> for all requests made even though all the Solr nodes are coming up just fine.  



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