[
https://issues.apache.org/jira/browse/COUCHDB-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943660#comment-14943660
]
ASF GitHub Bot commented on COUCHDB-2834:
-----------------------------------------
Github user nickva commented on the pull request:
https://github.com/apache/couchdb-couch-replicator/pull/19#issuecomment-145599470
@rnewson @davisp @kxepal
When processing the request we set mochiweb_request_recv = true in the
process dictionary too late. That makes it return Connection: close. ibrowse
used to ignore Connection: close and just kept the socket open. Then ibrowse
was fixed and revealed the issue.
Here is a potential fix and the details:
https://issues.apache.org/jira/browse/COUCHDB-2834
> Server sends connection: close too early
> ----------------------------------------
>
> Key: COUCHDB-2834
> URL: https://issues.apache.org/jira/browse/COUCHDB-2834
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Nick Vatamaniuc
>
> This is related COUCHDB-2833.
> This was found investigating the failure of replication tests. Specifically
> couch_replicator_large_atts_tests, the {local, remote} sub-case.
> The test sets up push replications from local to remote.
> Replication workers have more than 1 document larger than
> MAX_BULK_ATT_SIZE=64K. They start pushing them to the target, using a
> keep-alive connection (default for HTTP 1.1), the first few pipelined
> requests will go through using the same connection, then server will accept
> the first PUT to …/docid?edits=false, then return Connection:close and close
> the connection after the 201 Created result.
> Server should not close request too early and instead keep it open longer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
