[
https://issues.apache.org/jira/browse/SOLR-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066644#comment-15066644
]
Mark Miller commented on SOLR-8450:
-----------------------------------
That should be okay as things stands then. We on the fact that if the full
request was not sent, the update should not have happened, and a retry should
be fine.
bq. Because Solr throws a bad version exception and completes processing the
request, Jetty closes the connection before the client can send the rest of
frames.
Perhaps we can fix that then? Should we be cutting off the client like this? It
seems like this case should follow a normal, client sends full request, server
responds with full response flow?
> Internal HttpClient used in SolrJ is retries requests by default
> ----------------------------------------------------------------
>
> Key: SOLR-8450
> URL: https://issues.apache.org/jira/browse/SOLR-8450
> Project: Solr
> Issue Type: Bug
> Components: clients - java, SolrJ
> Reporter: Shalin Shekhar Mangar
> Fix For: 5.5, Trunk
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
