[
https://issues.apache.org/jira/browse/SOLR-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068279#comment-15068279
]
Mark Miller commented on SOLR-8453:
-----------------------------------
I have not seen any failures due to that change and have been running it for a
lot of days. I don't know that it's very important for this issue though - I'll
probably pare a couple of those things out or into their own issues. I think
most tests now are actually using that wait till cores are loaded option
anyway? Logically, this does make more sense to me though.
I'm still fighting with some DIH tests a little. There test classes really want
the old processor throws out exception behavior - and while I can easily
simulate that, it seems that also leaves those tests with the random connection
reset issue.
> Local exceptions in DistributedUpdateProcessor should not cut off an ongoing
> request.
> -------------------------------------------------------------------------------------
>
> Key: SOLR-8453
> URL: https://issues.apache.org/jira/browse/SOLR-8453
> Project: Solr
> Issue Type: Bug
> Reporter: Mark Miller
> Assignee: Mark Miller
> Attachments: SOLR-8453.patch, SOLR-8453.patch, SOLR-8453.patch,
> SOLR-8453.patch, SOLR-8453.patch
>
>
> The basic problem is that when we are streaming in updates via a client, an
> update can fail in a way that further updates in the request will not be
> processed, but not in a way that causes the client to stop streaming more
> updates.
> This seems to mean that even after the server stops processing the request,
> the concurrent update client is sending out some further updates. It seems
> previously this burst was sent on the connection and ignored? But after the
> Jetty upgrade from 9.2 to 9.3, Jetty closes the connection on the server when
> we throw certain document level exceptions, and the client does not end up
> getting notified of the original exception at all and instead hits a
> connection reset exception. Even before this update, it does not seem like we
> are acting in a safe or 'behaved' manner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
