Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 1.1.2
-
Fix Version/s: 1.1.7
-
Component/s: library
-
Security Level: Public
-
Labels:None
-
Environment:3 node cluster of 2.0, one memcached bucket authenticated, Couchbase Java Client 1.1.2 with required spymemcached 2.8.11
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.
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.
one quick update.. I don't know yet if its related, but you've been using the wrong netty version.. your logs show /Users/ingenthr/lib/netty-3.2.5.Final.jar' but the correct one is 3.5.5!
Since netty handles the streaming connection, this may be related - I dont know yet.