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

client does not handle failure of EPT node with memcached bucket

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Fix
    • Critical
    • 1.1.7
    • 1.1.2
    • Core
    • Security Level: Public
    • None
    • 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.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            daschl Michael Nitschinger
            ingenthr Matt Ingenthron
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty