Missing documents after replication


#1

We are currently trying to replicate data from bucketA to bucketB. We have performed the following command:

curl -X POST --header ‘Content-Type: application/json’ --header ‘Accept: application/json’ -d ‘{ “source”: “bucketA”, “target”: “http://localhost:4985/bucketB”, “continuous”: false }’ ‘http://localhost:4985/_replicate

This command runs succesfull. Afterwards, we have checked the number of documents in both buckets and noticed we are missing 12 documents in bucketB. After investigation, the 12 missing documents have 1 thing in common: they have multiple seq numbers:

,{“seq”:“2967038::2967285”,“id”:“b12682f6-a2c8-4f4f-b92b-25cdb409e9d6”,“changes”:[{“rev”:“18-ea89e9b2d18de3021b99795b999b212a”}]}
,{“seq”:“2967038::2967589”,“id”:“8b77aa77-219a-4ec1-a79b-c0492f5343f5”,“changes”:[{“rev”:“21-7ce91dcd4454259df32b33b9212bef9f”}]}
,{“seq”:“2967038::2967718”,“id”:“fdda4d4b-0590-4fb7-9286-5b76fda95e64”,“changes”:[{“rev”:“9-8c70efa19009fab36d60769d53c948d3”}]}
,{“seq”:“2967038::2967991”,“id”:“bf257288-bc8a-47a4-ab9d-e9e1953a0b08”,“changes”:[{“rev”:“42-55515cfe5b8bf207606e51b9acc30a83”}]}
,{“seq”:“2967038::2967998”,“id”:“1988e151-41ab-492c-b9f1-693872a5c6f0”,“changes”:[{“rev”:“20-6e7a206500482420eedccfe674e4a673”}]}
,{“seq”:“2967038::2968020”,“id”:“ced718c8-8ee8-46f6-bae9-3beb7286f76c”,“changes”:[{“rev”:“46-e3e310f71a01db553a496aa0169bcb3d”}]}
,{“seq”:“2967038::2969676”,“id”:“8a504858-c070-48d6-b5f8-04a1e26741aa”,“changes”:[{“rev”:“13-48853be764b9ab222338a413e97522f4”}]}
,{“seq”:“2967038::2969952”,“id”:“5dfb2a32-6736-4d21-a0aa-eb7fbeb4a8c4”,“changes”:[{“rev”:“38-52cb1d9bed7300df7650e367e150280c”}]}
,{“seq”:“2967038::2970030”,“id”:“91ce387a-8ea1-4888-aeda-c0887ecc693d”,“changes”:[{“rev”:“6-b2d7201d31e7329bd450e86b5c75affa”}]}
,{“seq”:“2967038::2970520”,“id”:“30b31bbf-3a26-4e8d-b3b0-6a8162ea666d”,“changes”:[{“rev”:“18-0fce785865a20631c981fbf568f31f74”}]}
,{“seq”:“2967038::2970621”,“id”:“54144295-c603-4514-8df9-cf584c9799ba”,“changes”:[{“rev”:“22-d2d2c15294aa6b43370bf92e99ea2efb”}]}
,{“seq”:“2967038::2970752”,“id”:“36f312b9-863d-4e95-86bc-279aa37425f7”,“changes”:[{“rev”:“5-05f04268178a7027d026a774b87a4104”}]}
,{“seq”:“2967038::2970756”,“id”:“4a5f933a-c747-4ed7-ac16-c1b60076ee8b”,“changes”:[{“rev”:“11-e0c58c0ba24fd70f11177ea10e3b911f”}]}

All other documents have a single seq number.


#2

What version of sync gateway are you using?


#3

We are using v1.5.1. but it is possible those docs are in the bucket from when we were using v1.4


#4

@nbrys,

Looks like SG Replication is having trouble with a buffered sequence number.

Could you report the issue here. https://github.com/couchbase/sync_gateway/issues


#5

It seems that after a while those 12 docs got a normal seq id. I have retriggered the replication but those 12 docs are still missing from bucketB


#6

When you say you can’t find documents in the Couchbase web interface (I assume this is the Couchbase Server Admin Console- these are documents that have been successfully replicated from Device 2 to Device 1? Are you able to retrieve these documents via the Sync Gateway Admin REST API (doing a simple GET on the doc id)?