Details
-
Bug
-
Resolution: Won't Do
-
Major
-
2.0.1
-
Security Level: Public
-
Operating System:
CentOS release 6.3 (Final) 64-bit
CPU Info:
4 processor and every processor has the same configuration:
model name : Intel(R) Xeon(R) CPU E31220 @ 3.10GHz
cpu MHz : 1600.000
cache size : 8192 KB
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtualOperating System: CentOS release 6.3 (Final) 64-bit CPU Info: 4 processor and every processor has the same configuration: model name : Intel(R) Xeon(R) CPU E31220 @ 3.10GHz cpu MHz : 1600.000 cache size : 8192 KB clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual
-
Untriaged
-
Centos 64-bit
-
Impediment
Description
My cluster has three buckets,and 8 nodes. In one bucket, one node has a strange phenomenon：
1. The ops of the key not exists in bucket is very high, and it up to 1.1k/s, see also in attach1.jpg;
2. Only one node has the exception, other nodes is ok, see also in attach2.jpg;
3. The exception node's status see in attach3.jpg;
4. The exception node VBUCKET RESOURCES see in attach4.jpg;
5. When I set the exception key in the bucket by manual, the ops is also up to 1.1k/s, and then delete it from bucket, the ops also not down;
