Uploaded image for project: 'Couchbase Java Client'
  1. Couchbase Java Client
  2. JCBC-70

Client fails to reconnect to server of non-default memcached bucket after failover and add back

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Duplicate
    • Affects Version/s: 1.0.3
    • Fix Version/s: 1.1.2
    • Component/s: Core
    • Security Level: Public
    • Labels:

      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.

        Issue Links

          Activity

            People

            • Assignee:
              daschl Michael Nitschinger
              Reporter:
              perry Perry Krug
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes