[
https://issues.apache.org/jira/browse/SOLR-17607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933665#comment-17933665
]
David Smiley commented on SOLR-17607:
-------------------------------------
With my PR; there is no retry-timeout. ZkClientClusterStateProvider has none
either. But the situation of concern isn't permanent... if another request
comes later once Solr is up, it will succeed at that time.
> HTTP ClusterStateProvider should defer talking to Solr until first use
> ----------------------------------------------------------------------
>
> Key: SOLR-17607
> URL: https://issues.apache.org/jira/browse/SOLR-17607
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud, SolrJ
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When using CloudSolrClient with HTTP URLs to get the ClusterState (HTTP
> ClusterStateProvider), it will talk to Solr when the client is created to
> fetch the live nodes. But maybe Solr isn't available at this time; it's
> annoying to require that Solr is available at the time that the
> CloudSolrClient is constructed. The ZK one is deferred till first use; I
> propose the same behavior for HTTP.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
