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

Adding a node to an existing cluster causes issues with a running memcached bucket

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 1.1.5
    • 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 adding a node to a cluster, I'd observed a number of AssertionErrors and some very odd errors about connections being null.

      This popped up when I wasn't expecting an issue, so I'm a bit surprised. The scenario I think is:

      Steps to reproduce:
      1. Have two nodes running (.200 and .201 in my case here)
      2. Add another node (.202 in my case here)

      See the logs for what detail is available.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JCBC-267 Memcached bucket still fails with all workloads

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JCBC-272 removing non-bootstrap node with memcached bucket okay, but adding the same node results in failures

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          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