wohali commented on issue #745: Replication with attachments never completes,
{mp_parser_died,noproc} error
URL: https://github.com/apache/couchdb/issues/745#issuecomment-369447881
So in testing with a client, this no longer hangs/crashes/eats all the RAM,
but it does still cause an issue where a too-large request body fails to
transmit a document. The replicator thinks it HAS successfully transferred the
document, and declares replication successful. A subsequent attempt to GET the
document results in a 404.
Here is a censored excerpt from the logfile of the situation:
```
[notice] 2018-02-27T01:16:58.004513Z [email protected] <0.31509.279>
0f1a3bf01b localhost:5984 127.0.0.1 undefined GET
/_scheduler/docs/_replicator/862944988a0e42e8e7567da18c863571 200 ok 0
[notice] 2018-02-27T01:17:07.843508Z [email protected] <0.24829.275>
-------- Starting replication 2def458d381dd99fa1f4e4887b5b9775+create_target
(http://localhost:5984/db1/ -> http://localhost:5984/db2/) from doc
_replicator:862944988a0e42e8e7567da18c863571 worker_procesess:4
worker_batch_size:500 session_id:bfafe761a21c1ea012228fc2df6790a9
[notice] 2018-02-27T01:17:07.843558Z [email protected] <0.24829.275>
-------- Document `862944988a0e42e8e7567da18c863571` triggered replication
`2def458d381dd99fa1f4e4887b5b9775+create_target`
[error] 2018-02-27T01:17:10.869278Z [email protected] <0.23437.278> --------
Replicator: error writing document `foo` to `http://localhost:5984/db2/`:
{error,request_body_too_large}
[notice] 2018-02-27T01:17:27.107006Z [email protected] <0.24829.275>
-------- Replication `2def458d381dd99fa1f4e4887b5b9775+create_target` completed
(triggered by `862944988a0e42e8e7567da18c863571`)
[notice] 2018-02-27T01:18:05.754340Z [email protected] <0.24230.274>
2a9c5d5507 localhost:5984 127.0.0.1 undefined GET /db2/foo 404 ok 1
```
Note that in extensive testing, this has only happened once, so I'm not sure
I can provide an easy reproducer here.
Couch was running at the info log level for this test, so I'm going bump it
up to debug level and try the test again, hoping for a duplicate.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
