> On Apr 29, 2015, at 11:50 AM, Jeremy Kelley <[email protected]> wrote: > > Just to follow up, I did some digging and realized this pruning with > sync_gateway based on revs_limit doesn't take place until after a document > update. So I updated a document. I am still seeing no change in the number > of revs coming down during the intial sync.
Does the document have a lot of (resolved or unresolved) conflicts? SG’s current rev-pruning algorithm has the problem that it won’t prune revisions that are recent ancestors of any leaf revision, even a deletion tombstone. That means that if you have a document with a zillion revisions, but there’s a conflict branch at least every revs_limit generations, nothing ever gets pruned. We just fixed this for SG 1.1, and we have confirmation from a customer that it fixed an issue like yours. You could try building your own SG from the ‘release/1.1.0’ branch and see if it helps you. Or wait a week or two* for the 1.1 developer preview release. —Jens * timing not guaranteed -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/D3A26AB4-55A9-4611-A290-96A5EA6A63BE%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
