[
https://issues.apache.org/jira/browse/SOLR-16129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515193#comment-17515193
]
Ishan Chattopadhyaya edited comment on SOLR-16129 at 3/31/22, 9:28 AM:
-----------------------------------------------------------------------
Tried to run solr-bench against main (jira/solr-16129 branch). Seems like
CloudSolrClient (8.x) couldn't talk to latest main.
{code}
Exception in thread "main" org.apache.solr.common.SolrException: Cannot connect
to cluster at localhost:2181: cluster not found/not ready
at
org.apache.solr.common.cloud.ZkStateReader.createClusterStateWatchersAndUpdate(ZkStateReader.java:505)
at
org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider.getZkStateReader(ZkClientClusterStateProvider.java:177)
at
org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider.getClusterState(ZkClientClusterStateProvider.java:119)
at
org.apache.solr.benchmarks.solrcloud.SolrCloud.init(SolrCloud.java:164)
at StressMain.main(StressMain.java:69)
{code}
-Can this be ported to branch_8_11 by any chance (to facilitate testing,
without updating solr-bench)?-
Edit: Thanks to [~janhoy], upgrading to 8.11.1 version of SolrJ solves this
problem.
was (Author: ichattopadhyaya):
Tried to run solr-bench against main (jira/solr-16129 branch). Seems like
CloudSolrClient (8.x) couldn't talk to latest main.
{code}
Exception in thread "main" org.apache.solr.common.SolrException: Cannot connect
to cluster at localhost:2181: cluster not found/not ready
at
org.apache.solr.common.cloud.ZkStateReader.createClusterStateWatchersAndUpdate(ZkStateReader.java:505)
at
org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider.getZkStateReader(ZkClientClusterStateProvider.java:177)
at
org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider.getClusterState(ZkClientClusterStateProvider.java:119)
at
org.apache.solr.benchmarks.solrcloud.SolrCloud.init(SolrCloud.java:164)
at StressMain.main(StressMain.java:69)
{code}
Can this be ported to branch_8_11 by any chance (to facilitate testing, without
updating solr-bench)?
> Solr specific InputStreamResponseListener to prevent client threads from
> hanging forever
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-16129
> URL: https://issues.apache.org/jira/browse/SOLR-16129
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-16129.patch
>
>
> This issue tracks the implementation of workaround I suggested for SOLR-16099
> - it does not _fix_ the underlying bug (which as of this writting doesn't
> have an identified root cause) but it does ensure that client threads which
> encounter the bug won't hang forever...
> {quote}One thing we may want to consider (in Solr) is replacing our usage of
> {{InputStreamResponseListener}} with a variant implementation that uses a
> "timeout" instead of an unlimited {{wait()}} (along the lines of a [spin-off
> jetty enhancement issue|https://github.com/eclipse/jetty.project/issues/7259]
> one of the jetty devs filed). We could probably (with some effort) tweak the
> impacted Solr APIs to propogate the (remaining) {{timeAllowed}} (if that
> option was specified) down to this class – and/or have an "extreme" default
> (ie: 30min) just to prevent threads from sticking around forever.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]