Resolution: Won't Fix
Affects Version/s: 1.1.2
Fix Version/s: 1.1.7
Security Level: Public
Environment:3 node cluster of 2.0, one memcached bucket authenticated, Couchbase Java Client 1.1.2 with required spymemcached 2.8.11
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
The client sees the config dropped, but doesn't reconfigure.
Client bootstraps off of one of the other nodes.
Attached file shows the config log in this case.