lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Wilkins (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-8453) Jetty update from 9.2 to 9.3 causes the server to reset formerly legitimate client connections.
Date Wed, 17 Feb 2016 09:27:18 GMT

    [ https://issues.apache.org/jira/browse/SOLR-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150173#comment-15150173
] 

Greg Wilkins commented on SOLR-8453:
------------------------------------

If solr is in the habit of not consuming the content AND is particular about how such connections
are closed/reused, then I believe a filter should be applied to all requests.
I will have a look again to see if jetty can provide consumeAll behaviour as an option, but
I really think that is just making solr dependent on a container features... as it was when
it assumed the container would consume all of the input on it's behalf - which is behaviour
not covered by any spec I know of.

Other than that, you could make a feature request on the client to be able to handle request
sending errors separately to response processing.  Ie in this case may receive a valid response
and the request body send still failed.



> Jetty update from 9.2 to 9.3 causes the server to reset formerly legitimate client connections.
> -----------------------------------------------------------------------------------------------
>
>                 Key: SOLR-8453
>                 URL: https://issues.apache.org/jira/browse/SOLR-8453
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 5.5, master
>
>         Attachments: SOLR-8453.patch, SOLR-8453.patch, SOLR-8453.patch, SOLR-8453.patch,
SOLR-8453.patch, SOLR-8453.patch, SOLR-8453.patch, SOLR-8453.patch, SOLR-8453.patch, SOLR-8453_test.patch,
SOLR-8453_test.patch, jetty9.2.pcapng, jetty9.3.pcapng
>
>
> 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 and finish up the request before the server does something
else with that connection.
> This seems to mean that even after the server stops processing the request, the concurrent
update client is still in the process of sending the request. It seems previously, Jetty would
not go after the connection very quickly after the server processing thread was stopped via
exception, and the client (usually?) had time to clean up properly. But after the Jetty upgrade
from 9.2 to 9.3, Jetty closes the connection on the server sooner than previous versions (?),
and the client does not end up getting notified of the original exception at all and instead
hits a connection reset exception. The result was random fails due to connection reset throughout
our tests and one particular test failing consistently. Even before this update, it does not
seem like we are acting in a safe or 'behaved' manner, but our version of Jetty was relaxed
enough (or a bug was fixed?) for our tests to work out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message