lite verision excessive _changes requests

[Sascha Lüdecke]

Hi all,

I have a problem with my Android app requesting the _changes multiple times per second over a long period in time. it is set up to have both a continuous pull and a push replication, the push replication filters some documents which shall not leave the device by a custom key.

I have not been able to find an explanation or a solution in the documentations of forums, does anybody have an idea (except upgrading) what is going on?

Couchbase lite Android: 1.0.4
Sync_gateway: 1.1.0 Comunity
couchbase server: 3.0.1 Community

The sync_gateway log contains a multitude of entries like this:

2015-09-21T02:58:13.101+02:00 HTTP: #4318592: POST /usercontent/_changes (as 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.178+02:00 Changes: MultiChangesFeed({*}, {Since:1368685 Limit:50 Conflicts:true IncludeDocs:false Wait:true Continuous:false Terminator:0xc20a9eea20 HeartbeatMs:300000 TimeoutMs:0}) ... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:13.102+02:00 HTTP: #4318591: POST /usercontent/_changes (as 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.178+02:00 Changes: MultiChangesFeed({*}, {Since:1368685 Limit:50 Conflicts:true IncludeDocs:false Wait:true Continuous:false Terminator:0xc20a9eeba0 HeartbeatMs:300000 TimeoutMs:0}) ... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.179+02:00 Changes+: MultiChangesFeed: channels expand to channels.TimedSet{"!":0x1, "5bead12ab8bce7c6a9dde51e4b202340":0x101b7e} ... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.179+02:00 Changes+: MultiChangesFeed waiting... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.179+02:00 Changes+: Waiting for "usercontent_production"'s count to pass 370
2015-09-21T02:58:14.179+02:00 Changes: MultiChangesFeed done (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:13.120+02:00 HTTP: #4318593: POST /usercontent/_changes (as 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.179+02:00 Changes: MultiChangesFeed({*}, {Since:1368685 Limit:50 Conflicts:true IncludeDocs:false Wait:true Continuous:false Terminator:0xc20a9ef080 HeartbeatMs:300000 TimeoutMs:0}) ... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.179+02:00 Changes+: MultiChangesFeed: channels expand to channels.TimedSet{"!":0x1, "5bead12ab8bce7c6a9dde51e4b202340":0x101b7e} ... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.179+02:00 Changes+: MultiChangesFeed waiting... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.179+02:00 Changes+: Waiting for "usercontent_production"'s count to pass 370
2015-09-21T02:58:14.179+02:00 Changes: MultiChangesFeed done (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.179+02:00 Changes+: MultiChangesFeed: channels expand to channels.TimedSet{"!":0x1, "5bead12ab8bce7c6a9dde51e4b202340":0x101b7e} ... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.179+02:00 Changes+: MultiChangesFeed waiting... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.179+02:00 Changes+: Waiting for "usercontent_production"'s count to pass 370
2015-09-21T02:58:14.179+02:00 Changes: MultiChangesFeed done (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.402+02:00 HTTP: #4318594: POST /usercontent/_changes (as 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.404+02:00 Changes: MultiChangesFeed({*}, {Since:1368685 Limit:50 Conflicts:true IncludeDocs:false Wait:true Continuous:false Terminator:0xc20a9ef800 HeartbeatMs:300000 TimeoutMs:0}) ... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.404+02:00 Changes+: MultiChangesFeed: channels expand to channels.TimedSet{"!":0x1, "5bead12ab8bce7c6a9dde51e4b202340":0x101b7e} ... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.404+02:00 Changes+: MultiChangesFeed waiting... (to 5bead12ab8bce7c6a9dde51e4b202340)
2015-09-21T02:58:14.404+02:00 Changes+: Waiting for "usercontent_production"'s count to pass 370
2015-09-21T02:58:14.404+02:00 Changes: MultiChangesFeed done (to 5bead12ab8bce7c6a9dde51e4b202340)

Best regards
Sascha

--
Sascha Lüdecke

[Jens Alfke]

This sounds like something that was fixed in Android version 1.1 — please try updating and see if you still have the problem.
(There were a lot of replication fixes/improvements in 1.1, so it’s definitely worth updating anyway.)

—Jens