Details
-
Bug
-
Resolution: Duplicate
-
Blocker
-
3.0
-
Security Level: Public
-
Platform = Physical
OS = CentOS 6.5
CPU = Intel Xeon E5-2630 (24 vCPU)
Memory = 64 GB
Disk = 2 x SSD
-
Untriaged
-
Centos 64-bit
-
-
Yes
Description
1 bucket x 100M x 2KB, 1 x 1 views, 10K mixed ops/sec, 400 qps
It happens in all rebalance cases (in/out/swap/failover), so it's either 3->4 or 4->3.
Not a new regression, I can see this issue in many 3.0 builds.
The latency is normally low but there are few occasional spikes. In 2.5.x peak latency was about 1-2 sec.
Attachments
Issue Links
- relates to
-
MB-11589 Sliding endseqno during initial index build or upr reading from disk snapshot results in longer stale=false query latency and index startup time
- Closed
-
MB-11919 3-5x increase in index size during rebalance with views
- Reopened
-
MB-11920 DCP based rebalance with views doesn't leverage faster indexing
- Closed