2.syncgateway replicator lagging so that updates to source till no ancestor revision is available in destination
I’d only expect this to occur if your revs_limit is set too low for your expected document update frequency. If you’re making more than revs_limit updates to a document before it can be replicated, you’ll need to increase revs_limit to avoid the scenario you’re describing.
we observed non-tombstoned conflicts are pruned from couchbase during traffic. we will try to reproduce and share the steps.
can you please let us know how to limit revision growth if revisions grows beyond revs_limit due to sg-replicate lagging