Views-Only/Config Cache workload does not receive cluster updates

Set up a three node cluster. Configure a PHP client doing regular views workload against this cluster using the configuration cache.

Remove one node of the cluster.

Expected behavior: the configuration would be updated and the clients would use the remaining two nodes.

Observed behavior: view requests are still going to that third node and responding with a 404, since the node is still up but the design document is not there since the node reverts to unconfigured.

I believe what may be happening here is the process which was originally doing the config stream exits and the only reason to do a configuration update would be a not_my_vbucket response. Since this is a view only workload, the 404s aren't a trigger to check for an updated configuration.