Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.0
-
Security Level: Public
-
None
-
Untriaged
-
Centos 64-bit
-
Unknown
Description
version: 3.0.0-805, centos-64, vbuckets=1024
1. Create 7 node cluster (10.6.2.144-150)
2. Create default bucket and add 1000 documents
3. Add Firewall restrictions to node 10.6.2.146
4. Full failover node 10.6.2.146
5. Rebalance the cluster
6. Check if unacked bytes = 0 for all existing nodes in a cluster
Issue observed
[root@palm-10307 bin]# ./cbstats 10.6.2.147:11210 upr | grep unacked
eq_uprq:replication:ns_1@10.6.2.147->ns_1@10.6.2.144:default:unacked_bytes: 0
eq_uprq:replication:ns_1@10.6.2.147->ns_1@10.6.2.145:default:unacked_bytes: 0
eq_uprq:replication:ns_1@10.6.2.147->ns_1@10.6.2.146:default:unacked_bytes: 28
eq_uprq:replication:ns_1@10.6.2.147->ns_1@10.6.2.148:default:unacked_bytes: 0
eq_uprq:replication:ns_1@10.6.2.147->ns_1@10.6.2.149:default:unacked_bytes: 0
eq_uprq:replication:ns_1@10.6.2.147->ns_1@10.6.2.150:default:unacked_bytes: 0
Above see how 10.6.2.146 upr stream has unacked bytes !=0