lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-4044) CloudSolrServer early connect problems
Date Thu, 06 Dec 2012 14:49:09 GMT


Yonik Seeley commented on SOLR-4044:

Hmmm, so if I'm understanding you correctly, if you start up the CloudSolrServer early, then
even after the cluster is ready, the CloudSolrServer never sees it as ready.

If the issue truly is in ZkStateReader, this may be an issue beyond CloudSolrServer and cause
problems in the servers themselves?  Or perhaps the code that creates all the collection template
stuff if none exists has been preventing this from being seen?

If it looks like there is no clusterstate.json it seems like we should have an option to bail
out immediately (with an appropriate error message).

Do we also need a mode that waits and retries for a certain amount of time?

> CloudSolrServer early connect problems
> --------------------------------------
>                 Key: SOLR-4044
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.0
>            Reporter: Grant Ingersoll
> 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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message