Details
-
Bug
-
Resolution: Fixed
-
Test Blocker
-
2.5.0, 3.0
-
Security Level: Public
-
Platform = Physical
OS = CentOS 6.5
CPU = Intel Xeon E5-2680 v2
Memory = 256 GB
Disk = RAID 10 SSD
-
Untriaged
-
Centos 64-bit
-
On demand.
-
No
Description
Setup:
1 -> 1, unidir, non-DGM, no compaction, xdcrOptimisticReplicationThreshold = 0.
Both capi and xmem.
Steps:
– Load data, wait for persistence
– Start replication to remote cluster
– Monitor replication rate, it should be high, something like 10-30K ops/sec
– Start front-end workload on source server (1000 updates/sec)
Observation:
– Replication rate drops to very low value (about 100 ops/sec)
– There is no obvious resource saturation
– "erlang:statistics(run_queues)." reports zero queues
– Nothing suspicious reported by "etop:start([
])." (though I'm not an expert).
Originally spotted in local test with emulated WAN effects (using netem on both sides). Confirmed in EC2 setup (east -> west).
Attachments
Issue Links
- relates to
-
MB-12274 2.5.1 Maintenance Patch-2 Release
- Closed