Description
In earlier tests with reconnecting to a node on failover we used default memcached bucket. But when we tested the same scenario with a non-default bucket, we noticed the client did not reconnect (due to a null pointer exception internally). I have attached the SDK logs for this scenario where we used "IndexByLniataData" memcached bucket. The problem presents when adding the node back after a failover.
11:34:43,411 DEBUG [Memcached IO over
{MemcachedConnection to /10.14.5.119:11210}] [CouchbaseMemcachedConnection] Selecting with delay of 3038ms
Exception in thread "Thread-3" java.lang.NullPointerException
at net.spy.memcached.auth.AuthThread.buildOperation(AuthThread.java:117)
at net.spy.memcached.auth.AuthThread.run(AuthThread.java:86)
Logs/stack trace attached.
Attachments
Issue Links
For Gerrit Dashboard: JCBC-70 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
21130,6 | JCBC-70: Fix Authentication to non-default bucket when connecting new node | release10 | couchbase-java-client | Status: MERGED | +2 | +1 |
21197,1 | JCBC-70: Fix Authentication to non-default bucket when connecting new node | master | couchbase-java-client | Status: ABANDONED | 0 | 0 |
22975,4 | JCBC-160: Merge current release 1.0 branch fixes in for 1.1. | master | couchbase-java-client | Status: MERGED | +2 | +1 |