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

Resize nodes: Rebalance failed as per couchbase-server but operator event says rebalance is success

    XMLWordPrintable

Details

    Description

      Scenario:

      1. Deploying cluster with 2 nodes with data, index, query and 3 nodes with eventing service
      2. Enabled eventing function with 3 buckets in cluster
      3. Running goroutine to insert data to src bucket in backgroud
      4. Initiate resize of analytics node to 4 nodes

      After adding an extra eventing node, rebalance is started and failed with the reason,

      Rebalance exited with reason {service_rebalance_failed,eventing, {badmatch, {error, {unknown_error, <<"Some apps are undergoing bootstrap">>}}}}

      But operator generated the event as "rebalance completed"

       

      Testcase name: TestEventingResizeCluster

      Attachments

        Issue Links

          For Gerrit Dashboard: K8S-479
          # Subject Branch Project Status CR V

          Activity

            simon.murray Simon Murray added a comment -

            Okay that is not the problem

            Rebalance exited with reason {service_rebalance_failed,cbas, {lost_connection,shutdown}}

            I suggest you raise a bug against CBAS.

            simon.murray Simon Murray added a comment - Okay that is not the problem Rebalance exited with reason {service_rebalance_failed,cbas, {lost_connection,shutdown }} I suggest you raise a bug against CBAS.

            Simon,

            Where did you see that CBAS message? I'm not seeing it in any of the logs.

            • Mike
            mikew Mike Wiederhold [X] (Inactive) added a comment - Simon, Where did you see that CBAS message? I'm not seeing it in any of the logs. Mike
            simon.murray Simon Murray added a comment -

            I think it was raised in the UI logs

            simon.murray Simon Murray added a comment - I think it was raised in the UI logs

            There are different problems that were both discussed on this issue. The problem in July caused by an eventing issue and the operator did the right thing. The problem in August is a duplicate of K8S-543.

            mikew Mike Wiederhold [X] (Inactive) added a comment - There are different problems that were both discussed on this issue. The problem in July caused by an eventing issue and the operator did the right thing. The problem in August is a duplicate of K8S-543 .

            Closing this bug.

            Verified this scenario using server build Enterprise Edition 6.0.0 build 1550 and operator 1.0.0-418

            ashwin.govindarajulu Ashwin Govindarajulu added a comment - Closing this bug. Verified this scenario using server build Enterprise Edition 6.0.0 build 1550 and operator 1.0.0-418

            People

              simon.murray Simon Murray
              ashwin.govindarajulu Ashwin Govindarajulu
              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