Indexer services not able to recover from a KV node going down and rebalance

1. Create a cluster of 4 nodes (1:kv+index,2:kv,3:index,4:index)
2. Create default bucket and load 100800 documents
3. Stop node -2 which hosts the kv
4. Create a secondary index
4. from UI do a graceful failover of the node and do a rebalance.

Verify the following:
a) Query status, expecting it should be online, since rebalance has happened:
Query is not online:
Ritams-MacBook-Pro:testrunner rsharma$ curl -u Administrator:password 172.23.106.75:8093/query -d 'statement=select * from system:indexes'
{
"requestID": "b7363d27-14a5-4f04-95e1-6d27394f691f",
"signature":

{ "*": "*" }

,
"results": [
],
"errors": [

{ "code": 12014, "msg": "error: Error Connecting KV 127.0.0.1:8091 Err 172.23.106.76:11210: dial tcp 172.23.106.76:11210: connection refused. Index employee73679e114d774875a0214b2dcd81ccd5job_title([`job_title`]). Index state: pending" }

],
"status": "errors",
"metrics":

{ "elapsedTime": "126.296725ms", "executionTime": "126.016899ms", "resultCount": 0, "resultSize": 0, "errorCount": 1 }

}

b) UI has multiple issues:
1. Shows up 2 indexes instead of one - known issue
2. Shows error.