Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
4.0.0
-
Security Level: Public
-
None
-
Untriaged
-
Unknown
-
Mar 9 - Mar 27
Description
Source:
https://s3.amazonaws.com/cb-customers/davidH/collectinfo-2015-04-17T112134-ns_1%40192.168.78.101.zip
https://s3.amazonaws.com/cb-customers/davidH/collectinfo-2015-04-17T112134-ns_1%40192.168.78.102.zip
https://s3.amazonaws.com/cb-customers/davidH/collectinfo-2015-04-17T112134-ns_1%40192.168.78.103.zip
Destination:
https://s3.amazonaws.com/cb-customers/davidH/collectinfo-2015-04-17T112221-ns_1%40192.168.78.104.zip
Uni-Directional XDCR from a 3 node cluster to a single node cluster. All running Build 1891 on Debian Linux.
Timeline was:
- Populate Source Dataset (via pillowfight)
- Enable XDCR from source to dest (all default options)
- Whilst the mutations were flowing I did delete around 10 documents from the source cluster via the UI.
- Replication reported as 100% complete at source (zero outstanding mutations)
- Observed that the source document count was 564541 and destination was 564099 (difference of 442).
There were no errors on the UI regarding any replication failures. cbcollects from both clusters attached.
Attachments
Issue Links
- relates to
-
MB-14647 Items expired unexpected and some weirdness in stats
- Closed