We have a very heavy write once a day which lasts for 1-2 hours and no more write again. It is found that xdcr didn’t finish. In fact, persisting to disk can not get completed before I deleted xdcr (about 6hours). When xdcr is deleted, disk write queue grows from 800k to 20M quickly and then decreased to 0; beam.smp reduced from 4.5g to 1.6g memory usage; after a while the docs fragments decreased from 43% to 41%.
So I guess, xdcr and persisting has some competition, which blocks persisting, fragment compacting, xdcr and even writing data(first 3 are about disk, the last is about buffer? ).
It seems an easy way to work around is having a scheduled xdcr, use a timer to start. Or, couchbase can detect that competition, and stop xdcr until the write completed.
Is there any other solutions I can try? Thanks.