Details
-
Bug
-
Resolution: Duplicate
-
Blocker
-
3.0
-
Security Level: Public
-
CentOS 6.x 8*8 clusters. Each node : 15GB RAM, 450Gb HDD
-
Untriaged
-
No
-
June 30 - July 18
Description
Build
--------
3.0.0-900(xdcr on upr, internal replication on upr)
Clusters
-----------
Source : http://172.23.105.44:8091/
Destination : http://172.23.105.54:8091/
There's currently a test running on this cluster. You can take a look if required.
Steps
--------
1. Load on both clusters till vb_active_resident_items_ratio < 50.
2. Setup bi-xdcr on "standardbucket", uni-xdcr on "standardbucket1"
3. Access phase with 50% gets, 50%deletes running now for an hour.
Problem
-------------
See screenshot. Mutation replication rate is uneven for uni and bi-xdcr.
Bucket under discussion: standardbucket1 (has uni-xdcr) has ~900K items remaining. Mutation replication is almost 0.
Another bucket standardbucket has bi-xdcr (to same cluster) but it's mutation replication rate is ~10k ops/sec, there's data moving as can be seen from upr queue stats.
Bucket capacity:5GB for both standard buckets.
Bucket priority
-----------------------
Both standardbucket and standardbucket1 have high priority.
Attaching cbcollect.