[
https://issues.apache.org/jira/browse/SOLR-17607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17934398#comment-17934398
]
ASF subversion and git services commented on SOLR-17607:
--------------------------------------------------------
Commit ff0f9050075543d64d6ccc760466a233c00863e8 in solr's branch
refs/heads/branch_9x from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=ff0f9050075 ]
SOLR-17607: Http ClusterStateProvider, lazy connect (#3249)
i.e. stop eagerly connecting when CloudSolrClient is created.
Update urlScheme on successful getLiveNodes
(cherry picked from commit 9918ee640dce7123ff51eb38d9eb1c6f4e06b487)
> 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 20m
> 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]
