I've been able to reproduce - it looks like this is down to deduplication of entries by doc ID on the Couchbase server feed that Sync Gateway uses to manage the _changes request. Multiple updates to the same doc are assigned different sequence numbers, and Sync Gateway currently buffers those sequence numbers to ensure data consistency for clients. When a sequence is deduplicated by the feed, Sync Gateway treats that as a still pending sequence, and blocks any further replication pending that sequence.
The existing fix on the master branch for issue #525 (https://github.com/couchbase/sync_gateway/issues/525) already provides a fix for the latency issues you're seeing - it allows Sync Gateway to stream subsequent changes while waiting for slow-arriving sequences. However, I've also filed an additional ticket to better handle the scenario where a sequence is not actually slow - it's been deduplicated by the Couchbase server feed. I'm tracking that here: https://github.com/couchbase/sync_gateway/issues/775 -- 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 mobile-couchbase+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/4abab079-14e3-44e8-89c5-31ea698c5c26%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
