[
https://issues.apache.org/jira/browse/COUCHDB-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15545494#comment-15545494
]
ASF subversion and git services commented on COUCHDB-3168:
----------------------------------------------------------
Commit e5747dbaa2fb10760eb2cd3e289a01b51694c7cd in couchdb-couch-replicator's
branch refs/heads/master from [~vatamane]
[
https://git-wip-us.apache.org/repos/asf?p=couchdb-couch-replicator.git;h=e5747db
]
Fix handling of 413 responses for single document PUT requests
When replicator finds a document which has an attachment size greater than 64k,
or has more than 8 attachments, it switches to a non-batching mode and posts
each document separately using a PUT request with a multipart/related
Content-Type.
Explicitly handle the case when the response to the PUT request is a 413. Skip
the document and dump `doc_write_failures` count, just like in the case of the
413 response for a _bulk_docs POST request.
Jira: COUCHDB-3168
> Replicator doesn't handle well writing documents to a target db which has a
> small max_document_size
> ---------------------------------------------------------------------------------------------------
>
> Key: COUCHDB-3168
> URL: https://issues.apache.org/jira/browse/COUCHDB-3168
> Project: CouchDB
> Issue Type: Bug
> Reporter: Nick Vatamaniuc
>
> If a target db has set a smaller document max size, replication crashes.
> It might make sense for the replication to not crash and instead treat
> document size as an implicit replication filter then display doc write
> failures in the stats / task info / completion record of normal replications.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
