Uploaded image for project: 'Java Couchbase JVM Core'
  1. Java Couchbase JVM Core
  2. JVMCBC-361

Node dispatching should occur on DEGRADED

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.3.2
    • 1.3.3
    • Services
    • None

    Description

      When opening several buckets in a row, one of which is tried with
      wrong password in the middle, the opening of last buckets can timeout.

      During investigation it was seen that in a goodA/wrong/goodB bucket open
      sequence, the CarrierRefresher would schedule a GetBucketConfigRequest
      for "goodA" and it would go into a long-lasting retry loop.

      Upon investigating further, it appears this is due to the ongoing
      attempt at opening "wrong", which puts the Node(s) into DEGRADED mode.
      Since the KeyValueLocator won't dispatch a message to a node that isn't
      CONNECTED, this goes directly into the retry loop even though the
      request could go through (the corresponding bucket's services are
      CONNECTED).

      Attachments

        Issue Links

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

          Activity

            There are no comments yet on this issue.

            People

              simonbasle Simon Baslé (Inactive)
              simonbasle Simon Baslé (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty