[ https://issues.apache.org/jira/browse/SOLR-16505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829251#comment-17829251 ]
David Smiley commented on SOLR-16505: ------------------------------------- Could be useful to distinguish two changes here – one is the change in HttpClient, but the other is Using a SolrClient vs HttpClient. So you could temporarily have the SolrClients created here based on Apache HttpClient and see if you get the same issues. If the issues persist, then there's probably an issue around sharing an HttpClient that gets closed in one SolrClient but is still referenced in a non-closed other SolrClient. Or simply using a SolrClient after closure was done; maybe it's a field. If the issues don't persist, then maybe this means the Apache HttpClient is tolerant to extra close calls but Jetty HttpClient isn't. > Switch UpdateShardHandler.getRecoveryOnlyHttpClient to Jetty HTTP2 > ------------------------------------------------------------------ > > Key: SOLR-16505 > URL: https://issues.apache.org/jira/browse/SOLR-16505 > Project: Solr > Issue Type: Sub-task > Reporter: David Smiley > Priority: Major > Time Spent: 3h 50m > Remaining Estimate: 0h > > This method and its callers (only RecoveryStrategy) should be converted to a > Jetty HTTP2 client. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org