Index build stuck after killing projector in a kv node in 5-node cluster

Run: http://qa.sc.couchbase.com/job/cen006-2i-vset03-03-recoverytests-add-index/82/consoleFull

Steps same as in MB-15793 except the process that killed is projector on the KV node 172.23.121.143

Indexes standard_bucket0:employeee655c7673a8d47a7aa9394532ff200c4job_title and standard_bucket0:employeee655c7673a8d47a7aa9394532ff200c4join_yr ON are both stuck at 21%

Logs:
https://s3-ap-southeast-1.amazonaws.com/indexing-test/addIndex_test25/collectinfo-2015-07-23T022626-ns_1%40172.23.121.141.zip
https://s3-ap-southeast-1.amazonaws.com/indexing-test/addIndex_test25/collectinfo-2015-07-23T022626-ns_1%40172.23.121.142.zip
https://s3-ap-southeast-1.amazonaws.com/indexing-test/addIndex_test25/collectinfo-2015-07-23T022626-ns_1%40172.23.121.143.zip
https://s3-ap-southeast-1.amazonaws.com/indexing-test/addIndex_test25/collectinfo-2015-07-23T022626-ns_1%40172.23.121.144.zip
https://s3-ap-southeast-1.amazonaws.com/indexing-test/addIndex_test25/collectinfo-2015-07-23T022626-ns_1%40172.23.121.145.zip

Cluster:
services_init=n1ql:kv-kv-kv-index-index
VMs: 172.23.121.141 to 172.23.121.145