beam.smp chewing up memory

I'm running a set of XDCR tests. My model is a master/slave environment, where the master cluster will always push data to the destinations. In my tests, i insert data into the master (which is a cluster of two nodes), which replicates to all the destinations. All is working well (your xdcr 2.2 improvements are a major improvement from 2.1). However, beam.smp (on the masters) is eating up memory, and eventually crashes. In both instances where beam.smp crashed, it starts up again and finishes the replication. Is this expected behavior?

1 Answer

« Back to question.


As you can guess this is not an expected behavior. (to have processes crashing); but I would like to understand a little more your topology.

Can you tell us how many nodes do you have on each cluster? and how many documents/operation per second do you have? (You can monitor the XDCR work on your administration console)

What are the options you have chosen for the replication itself, based on the parameters available here: