Details
Description
When investigating a case, it seems that the dropped configuration when using a memcached bucket is never reestablished. I'm not sure if this is because we rely on timeouts (which we won't get in this case) or something else.
Steps to reproduce:
1. Set up three node cluster
2. Run a constant workload, starting off of one of the nodes (192.168.1.200 in my config)
3. Remove that node from the cluster
Observed behavior:
The client sees the config dropped, but doesn't reconfigure.
Expected behavior:
Client bootstraps off of one of the other nodes.
Attached file shows the config log in this case.