[jira] [Updated] (SOLR-17538) CloudHttp2SolrClient needs a custom ClusterStateProvider option

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-17538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated SOLR-17538:
----------------------------------
    Labels: pull-request-available  (was: )

> 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: 10m
>  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: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org