{UPR}: unacked_bytes != 0 for views after rebalance-in

Discussed with Siri and Mike. Cluster:: 10.6.2.144-146

version:: 3.0.0-805,vbuckets=128

Was running a test case which does the following:

./testrunner -i ~/ini/palm.ini -t rebalance.rebalancein.RebalanceInTests.rebalance_in_with_queries,nodes_in=2,blob_generator=False,value_size=1024,enable_flow_control=True,verify_unacked_bytes=True,skip_cleanup=True,GROUP=IN;BASIC;P0;FROM_2_0

1. Create 2 node cluster (10.6.2.144,10.6.2.145)
2. Create default bucket with 1 K data
3. Create 5 views
4. Rebalance-in 1 node (10.6.2.146)
5. Check unacked bytes

In the end we check by using cbstats if all unacked bytes for upr flow control is ‘0’. We found the following

[root@palm-10307 bin]# ./cbstats 10.6.2.144:11210 upr | grep unacked
eq_uprq:mapreduce_view: default _design/dev_ddoc1 (prod/main):unacked_bytes: 148496
eq_uprq:mapreduce_view: default _design/dev_ddoc1 (prod/replica):unacked_bytes: 0
eq_uprq:replication:ns_1@10.6.2.144->ns_1@10.6.2.145:default:unacked_bytes: 0
eq_uprq:replication:ns_1@10.6.2.144->ns_1@10.6.2.146:default:unacked_bytes: 0
[root@palm-10307 bin]#

logs are attached