[
https://issues.apache.org/jira/browse/SOLR-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511485#comment-13511485
]
Yonik Seeley commented on SOLR-4044:
------------------------------------
bq. a fix may be as simple as allowing the cloudsolrserver or zkstatereader to
create the nodes it's expecting to watch if it doesn't find them.
A retry seems much safer... after all, someone could have given the wrong path.
Seems like clients should normally be read-only w.r.t. ZK.
> 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
> Fix For: 4.1
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
