Details
Description
Since all the N1QL test blocker has been resolved, I was able to run a first round of n1ql situational test.
The two situations which do not complete the n1ql queries are server restart and readd2 (fail over 2 nodes and readd the nodes to the cluster and rebalance)
Client does not run any n1ql query after 2 of the nodes restart in the server restart case, and there is no ops after the failover nodes are added back to the cluster.
I am using the latest client and core build with primary view index