Interesting. I think what's actually happening here is the same issue as
#673 - an unused sequence is being created on SG startup. However, the 60
second timeout (waiting for #11326) doesn't start until your first update
shows up on the the TAP feed:
02:39:08.911342 Cache: Received #11328 after 580ms
("59238463-B4DD-48CB-A607-D3701DBA794F" / "51-4a2a2fa5bce8750f1fb5d590ff24d907")
02:39:08.911352 Cache: Deferring #11328 (1 now waiting for #11326...#11327)
You could verify this in a couple of ways:
1. I'd expect this to be unrelated to making multiple updates on the same
document. Even updates on separate documents should hit this issue.
2. You could temporarily remove any user definitions from your config file -
that will avoid the unused sequence.
3. You could test using a build of SG master branch (which has the fix for #673)
When you originally hit this issue (the log from the first post on this
thread), do you remember whether it was for a Sync Gateway that had been
recently started? Since you were originally reporting this only for multiple
updates to a single document, and not different documents, it sounds like there
still may be more going on than just the 'unused sequence on startup' bug. If
you're able to reproduce the original issue, I'd really like to see the
details. One way to reproduce might be:
- restart SG
- send an single update (to trigger the timeout waiting for the unused sequence)
- wait for the timeout (60+ seconds)
- attempt multiple updates to a single doc, and see if you're able to reproduce
Thanks,
Adam
--
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/efdc8786-b2f1-4441-8be2-937ba74aa2e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
