Also, we host our own CouchDB server and use nginx as a reverse proxy. We 
already did the same purge approach before with TouchDB, but it is hard to 
tell if the issue is with CBL or CouchDB.

On Sunday, September 14, 2014 1:06:21 PM UTC-7, Jens Alfke wrote:
>
>
> On Sep 14, 2014, at 11:57 AM, dyowee <[email protected] <javascript:>> 
> wrote:
>
> We have this requirement to limit data being replicated, so we tried to do 
> a filtered replicated by marking old documents with archived=true. But then 
> we encountered the problem that CBL cannot sync anymore, saying 'WARNING 
> Truncated changes feed'
>
>
> Well, that sounds like a bug somewhere, not a limitation of filtered 
> replication.
>
> That warning occurs if the JSON parser hits a syntax error reading the 
> received _changes feed. It almost always means that the socket got closed 
> unexpectedly. And that in turn usually means an intermediate gateway 
> decided the socket's been open too long. (Some telco gateways will do this, 
> and apparently also AWS load balancers.) The 'heartbeat' option on the 
> _changes request is supposed to prevent this by telling the server to 
> periodically send a no-op CRLF so the socket doesn't look idle, though.
>
> In any case, this isn't something that's related to filtering, so it's 
> weird that it started happening after you added that. Do you have any more 
> clues?
>
> we had to completely restore the CouchDB databases
>
>
> What does that mean?
>
> Is there a better way to do filtered replication?
>
>
> Again, there's nothing wrong with what you're doing. It just seems to have 
> triggered some kind of bug, either in CBL or CouchDB. Let's try to diagnose 
> that.
>
> —Jens
>
>

-- 
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/cb533240-a299-4973-aa1f-b0a24542d677%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to