Hi Guys, i have a couchdb database (CouchDB 0.11.0) containing about 200 documents. The database has a very large update-sequence as it continuously gets added and removed documents. Meaning the overall document count stays low but lots of adds and removes. Replicating this database has been working fine for months.
I now had to change the URL of the source database. Now when i start pull replication the problem begins and the destination couch runs with about 100% on one cpu and eating up gigabytes of memory (had up to 12 gb before i had to kill it). The changes call response is quite large: _changes?style=all_docs&heartbeat=10000&since=81775&feed=normal HTTP/1.0" 200 23304061 Is this intended behavior. Any suggestions what i can do? The source database was compacted before starting the replication. Best regards Simon -- Simon Eisenmann [ mailto:[email protected] ] [ struktur AG | Kronenstraße 22a | D-70173 Stuttgart ] [ T. +49.711.896656.0 | F.+49.711.89665610 ] [ http://www.struktur.de | mailto:[email protected] ]
smime.p7s
Description: S/MIME cryptographic signature
