You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Grant Ingersoll (JIRA)" <ji...@apache.org> on 2012/11/07 12:49:12 UTC
[jira] [Created] (SOLR-4044) CloudSolrServer early connect problems
Grant Ingersoll created SOLR-4044:
-------------------------------------
Summary: 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
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-4044) CloudSolrServer early connect
problems
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510718#comment-13510718 ]
Grant Ingersoll commented on SOLR-4044:
---------------------------------------
I think this also happens even if connect is called via the process() method. AFAICT, from reading the code, it is due to ZkStateReader being instantiated once in the connect string, but not really being notified if/when cores/collections are available b/c it doesn't have anything it can set watches on.
I will try to write up a test to see if I can reproduce this.
> 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
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Comment Edited] (SOLR-4044) CloudSolrServer early connect
problems
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510718#comment-13510718 ]
Grant Ingersoll edited comment on SOLR-4044 at 12/5/12 7:50 PM:
----------------------------------------------------------------
I think this also happens even if connect is called via the process() method. AFAICT, from reading the code, it is due to ZkStateReader being instantiated once in the connect string, but not really being notified if/when cores/collections are available b/c it doesn't have anything it can set watches on, yet, b/c Solr may not be ready yet.
I will try to write up a test to see if I can reproduce this.
was (Author: gsingers):
I think this also happens even if connect is called via the process() method. AFAICT, from reading the code, it is due to ZkStateReader being instantiated once in the connect string, but not really being notified if/when cores/collections are available b/c it doesn't have anything it can set watches on, yet, b/c Solr may not be up yet.
I will try to write up a test to see if I can reproduce this.
> 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
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Comment Edited] (SOLR-4044) CloudSolrServer early connect
problems
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510718#comment-13510718 ]
Grant Ingersoll edited comment on SOLR-4044 at 12/5/12 7:50 PM:
----------------------------------------------------------------
I think this also happens even if connect is called via the process() method. AFAICT, from reading the code, it is due to ZkStateReader being instantiated once in the connect string, but not really being notified if/when cores/collections are available b/c it doesn't have anything it can set watches on, yet, b/c Solr may not be up yet.
I will try to write up a test to see if I can reproduce this.
was (Author: gsingers):
I think this also happens even if connect is called via the process() method. AFAICT, from reading the code, it is due to ZkStateReader being instantiated once in the connect string, but not really being notified if/when cores/collections are available b/c it doesn't have anything it can set watches on.
I will try to write up a test to see if I can reproduce this.
> 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
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org