thanks for reporting this. We'll need a bit more info to make headway on this; the error message you see is a relatively unimportant part of the Erlang VM.
If you can start your instance up, I'm interested in a couple of specific things:
what the last update sequence number of your registry copy is:
should return a JSON blob like this:
Also, if you can make the couch.log file available (privately is fine, firstname.lastname@example.org GPG key for optional signing http://people.apache.org/~dch/KEYS) we might find something more enlightening.
Previous occurences of the error you mentioned have all been related to insufficient memory. FWIW I'm running replication < 2GB RAM atm on a gce small instance, 2 cores, and that's cpu bound only.
You can try reducing the parallelisation of replication; reduce:
- worker_batch_size to ease RAM pressure
- worker_processes for disk & network IO
Other Couch folk report reducing these right down has helped a lot initially.
Full info is here https://couchdb.readthedocs.org/en/latest/config/replicator.html
Current parameters can be seen via GET /_config/replicator, and you can do updates via PUT or also via futon's configuation interface. This will avoid the need to restart couchdb, which is only required if you edit the ini file by hand.
Bear in mind that a heavy load is borne by the central registry atm, there may not be a great deal you can influence on your local node wrt to performance.