Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-2690

Document Eventing DCP connection names with > 200 characters will fail Rebalance in 6.6.5

    XMLWordPrintable

Details

    • Page
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.3.0
    • documentation
    • 13: Release, Tools Bootstrap
    • 1

    Description

      KV made the change to restrict DCP feed name length to 200 characters in 7.0.0: https://issues.couchbase.com/browse/MB-34280 

      This change was picked up by Eventing in 7.0.0 as well: https://issues.couchbase.com/browse/MB-42968 (Your glorious ticket back in 2020)

      Kv team then backported this DCP change to 6.6.5: https://issues.couchbase.com/browse/MB-49271

      However, Eventing team was not aware of this change in 6.6.5 made by kv. This breaks Rebalance Operation in v6.6.5 when there are usually >~3 nodes in the cluster with Eventing function deployed at the same time. 

      We do not see this issue with 6.6.4(both kv,eventing did not make the DCP length change) and 7.0.x(both kv, eventing made the DCP length change).

      With 6.6.5: kv made the DCP length change, Eventing did not.

      Why did we not see this issue with 2.2.x: Because 6.6.5 was released unofficially in January and officially in early March this year(2022): https://issues.couchbase.com/browse/MB-47673

      The Eventing change is coming in 6.6.6(no idea about the timeline): https://issues.couchbase.com/browse/MB-51435 

      Attachments

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

        Activity

          simon.murray Simon Murray added a comment -

          Needs adding to the known issues.  Text:

          Kubernetes resource names are based on DNS, and may be up to ~250 characters in length.  Prior to Couchbase Server versions 6.6.5 and 7.0.0, these host names would be used to generate a key for internal communication, however long names caused a buffer overflow.  While this was fixed in 6.6.5 and 7.0.0, it wasn't fully implemented in 6.6.5, in particular for the eventing service.  When using long namespace or cluster names, ensure that you use a version of Couchbase Server greater than 6.6.5 or 7.0.0.

          Or something of that ilk

          simon.murray Simon Murray added a comment - Needs adding to the known issues.  Text: Kubernetes resource names are based on DNS, and may be up to ~250 characters in length.  Prior to Couchbase Server versions 6.6.5 and 7.0.0, these host names would be used to generate a key for internal communication, however long names caused a buffer overflow.  While this was fixed in 6.6.5 and 7.0.0, it wasn't fully implemented in 6.6.5, in particular for the eventing service.  When using long namespace or cluster names, ensure that you use a version of Couchbase Server greater than 6.6.5 or 7.0.0. Or something of that ilk
          simon.murray Simon Murray added a comment -

          I think this is in your court now, feel free to pass the buck to Steve.

          simon.murray Simon Murray added a comment - I think this is in your court now, feel free to pass the buck to Steve.

          Believed to be ready for QE validation.

          ingenthr Matt Ingenthron added a comment - Believed to be ready for QE validation.
          roo.thorp Roo Thorp added a comment -

          This looks good - showing up in the release notes. I guess we'll need to note if this is going to be fixed with 6.6.6?

          roo.thorp Roo Thorp added a comment - This looks good - showing up in the release notes. I guess we'll need to note if this is going to be fixed with 6.6.6?

          People

            roo.thorp Roo Thorp
            prateek.kumar Prateek Kumar (Inactive)
            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