[
https://issues.apache.org/jira/browse/SOLR-17538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895637#comment-17895637
]
ASF subversion and git services commented on SOLR-17538:
--------------------------------------------------------
Commit 783d7805ea7ef6defcb87cdec55a662935a938fb in solr's branch
refs/heads/main from Sanjay Dutt
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=783d7805ea7 ]
SOLR-17538: CloudHttp2SolrClient needs a custom ClusterStateProvider option
(#2832)
* SOLR-17538: CloudHttp2SolrClient needs a custom ClusterStateProvider option
---------
Co-authored-by: David Smiley <[email protected]>
> CloudHttp2SolrClient needs a custom ClusterStateProvider option
> ---------------------------------------------------------------
>
> Key: SOLR-17538
> URL: https://issues.apache.org/jira/browse/SOLR-17538
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ
> Reporter: David Smiley
> Assignee: Sanjay Dutt
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> It's currently _impossible_ to create a CloudHttp2SolrClient with a custom
> ClusterStateProvider, e.g. a ZkClientClusterStateProvider with an existing
> ZkStateReader. This issue aims to address that somehow.
> CloudLegacySolrClient _does_ have this ability!
> It must be addressed (and used in ZkController) to prevent a possible
> performance regression [here|https://github.com/apache/solr/pull/2751], which
> switched from a CloudLegacySolrClient to CloudHttp2SolrClient but without
> using the existing ZkStateReader and possibly a chroot bug (?).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
