Handling revision growth

Mobile
1

we could see that revision limit is growing in _sync due to below

  1. revision conflicts
  2. syncgateway replicator lagging so that updates to source till no ancestor revision is available in destination

we have used https://developer.couchbase.com/documentation/mobile/current/guides/sync-gateway/resolving-conflicts/index.html

but seems like it is not handling in all path,

  1. when one of conflicted revision pruned from couchbase
  2. does not handle point 2 in above scenario
  3. some cases _open_revs returning already deleted revision
    Limiting revisions on Couchbase Sync
2

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.

3

Thanks @adamf for quick one. we will sure try by increasing revs_limit.

am more interested in limit the revisions growth to revs_limit if any case if we end up in revisions growth(without revision conflicts )more than revs_limit,

Any luck on below.

And sometimes seeing tombstoned conflicted revision appearing in _changes?active_only=true&style=all_docs.

4

There shouldn’t be a scenario where non-tombstoned conflicts are pruned. Can you provide some more specifics on what you’re referring to?

5

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

we used conflict resolution
https://developer.couchbase.com/documentation/mobile/current/guides/sync-gateway/resolving-conflicts/index.html
but _open_revs=all returning doc with revision which is deleted earlier. below is issue raised for same