[
https://issues.apache.org/jira/browse/SOLR-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352164#comment-14352164
]
Mark Miller commented on SOLR-6944:
-----------------------------------
Unfortunately, this is way more complicated than it looks. In this case, this
is all much more related to the proxy code than any real issue.
bq. it generally occurs on the first request after a Jetty has shutdown and
then been restarted
This is just when it almost always happens (but usually *only* if the proxy
code is involved!)
It happens randomly other places too though.
bq. call closeExpiredConnections() in a background thread
I've gone down that path (SOLR-4509). The reason that it's not committed is
that it actually makes random NoHttpResponseExceptions *more* common in our
tests.
> ReplicationFactorTest and HttpPartitionTest both fail with
> org.apache.http.NoHttpResponseException: The target server failed to respond
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-6944
> URL: https://issues.apache.org/jira/browse/SOLR-6944
> Project: Solr
> Issue Type: Test
> Reporter: Mark Miller
> Assignee: Mark Miller
> Attachments: SOLR-6944.patch
>
>
> Our only recourse is to do a client side retry on such errors. I have some
> retry code for this from SOLR-4509 that I will pull over here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
