Poll regularly for config updates

start a cluster with 2 query nodes
start cbc-n1qlback with some query
add a new query node to the cluster and rebalance
observe the request/sec per node

expected: topology changes should eb automatically picked up by the clients. after rebalance the new query node needs to be part of the round robin requests being sent to the cluster. however new node does not start taking traffic even after a long wait.

if the load is stopped and restarted, the requests do go to the newly added node as well. However this means topology changes would require a restart of the app servers. that does cause admin overhead and possibly failed requests for the app and downtime.