You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2015/03/04 22:28:39 UTC
[jira] [Commented] (SOLR-4044) CloudSolrServer early connect
problems
[ https://issues.apache.org/jira/browse/SOLR-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347594#comment-14347594 ]
Shalin Shekhar Mangar commented on SOLR-4044:
---------------------------------------------
I am hesitant to introduce a method called waitForCluster. Can we overload connect with a boolean waitForCluster and timeout parameters instead?
> 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.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