[
https://issues.apache.org/jira/browse/COUCHDB-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722250#comment-13722250
]
Zhiqing Rao commented on COUCHDB-1856:
--------------------------------------
Hi Dave, I have tweaked the configuration again, also set the batch_size to 1,
then I can completely replicate the database I want. Thanks very much.
However, I also find a way to reproduce the problem:
1) couchdb 1.3.1, win7 64bit;
2) create a database, with 10 files,each is about 14M JSON data, without
attached files;
3) replicate the database to another server by using the default replicate
configuration, with less than 600k/s network,
then the target couchdb server would hang since erl.exe consumes more than
2GB memory.
BTW, if I try with only 10 small json files, each with about 14M attched binary
files, then the replication is fine.
Please let me know if you need anything from me.
> hang and restart when replicate remotely of database that has doc > 10M, with
> 600kb/s network speed
> ---------------------------------------------------------------------------------------------------
>
> Key: COUCHDB-1856
> URL: https://issues.apache.org/jira/browse/COUCHDB-1856
> Project: CouchDB
> Issue Type: Bug
> Components: Replication
> Affects Versions: 1.3, 1.3.1
> Reporter: Zhiqing Rao
> Attachments: couch_replicate_hang_erl_process.jpg,
> couch_replicate_hang.log, couch_replicate_hang_networking.jpg
>
>
> When I remotely replicate a database that has doc > 10M, with 600kb/s network
> speed, in a win7 64bit platform with couchdb 1.3.1, the couchdb server will
> launch the replication, but erl.exe soon reach up to commiting > 2GB memory,
> then
> couchdb server hangs until a restart.
> Two things that might helpful:
> 1) It's fine for me to replicate the database in the same couchdb server (in
> the same machine);
> 2) My web browers, IE9/10, chrome, firefox, also hang or without response, at
> sometimes, when I open the documents in the database with URL;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
