Hi Adam,
thanks for your very fast reply and taking care of this.

1. Yes, it´s sg 1.0.4 but I guess the issue was in 1.0.3 too. And yes, it´s 
reproducible. If I do changes (updates) on one single document within 3 
seconds I will get the WARNING and the delayed replication.
2. I´ve put the complete log in 
Gist https://gist.github.com/domutom/3748f143f523a6ff95b4 from restarting 
sg.
there was no other traffic on sync gateway during the logging.

thanks,
dominik





Am Montag, 6. April 2015 23:40:18 UTC+2 schrieb Adam Fraser:
>
> Based on the "WARNING: changeCache: Giving up, accepting #11298 even 
> though #11297 is missing -- db.(*changeCache)._addPendingLogs() at 
> change_cache.go:320" message after the break in your logs, this looks like 
> a case of the initial revision (#11297) not appearing on the TAP feed, and 
> Sync Gateway blocking waiting for that revision.  
>
> What version of Sync Gateway are you running?  If it's 1.0.4, I expect the 
> increased time you're seeing is due to 
> https://github.com/couchbase/sync_gateway/issues/517.
>
> The timeout handling is addressed in master, based on the changes 
> delivered for https://github.com/couchbase/sync_gateway/issues/525 - it 
> no longer blocks waiting for slow sequences.
>
> However, I'd like to better understand the real root cause - i.e. why the 
> initial revision (#11297) isn't showing up on the TAP feed as expected.  A 
> few questions:
> 1. Is this consistently reproducible for frequent single-doc updates?
> 2. Can you upload (to a gist) the full logs for the 80s window, to shed 
> some light on what else is happening for the feed in that window?
>
> 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/63563e7a-cf51-41da-9f95-5e7a207dc9f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to