Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-7786

[RN 2.0.2] Frequent replication start error messages "Failed to grab remote bucket info, vbucket.." at start of replication.

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.1.0
    • Component/s: ns_server
    • Security Level: Public
    • Environment:
      2.0.1.-160-rel
    • Flagged:
      Release Note

      Description

      Seeing 2 issues when trying to setup replication for the first time between two clusters -

      1.Frequently seeing error messages on creating the 1st time replication from cluster1 to cluster2.
      "Failed to grab remote bucket info, vbucket.."

      Both the buckets on source/destination are available for a long period of time, so it does not look like it is an issue w/ bucket not being ready.

      I dont have logs on this currently, will add soon.

      Seeing this across platforms - linux / windows and on most 2.0.1 runs.

      2.Replication replicates data as expected, and these error messages persist for over an hour on the xdcr-last 10 errors. This gives user a wrong idea about the state of replication.

      The intial Replication-call should either wait long enough to avoid these errors/ figure out if something else can be done here.

      And also, how frequently do we clean up the xdcr-error messages on the console? Can we clear them sooner than current time?

        Issue Links

        # Subject Project Status CR V
        For Gerrit Dashboard: &For+MB-7786=message:MB-7786

          Activity

          Hide
          kzeller kzeller added a comment - - edited

          Relabeled in RN 2.0.2 as Fix. For earlier versions was in release notes as known issue.

          Show
          kzeller kzeller added a comment - - edited Relabeled in RN 2.0.2 as Fix. For earlier versions was in release notes as known issue.
          Hide
          maria Maria McDuff (Inactive) added a comment -

          pls verify / close.
          if issue is fixed, karen does not need to RN for 2.0.2

          Show
          maria Maria McDuff (Inactive) added a comment - pls verify / close. if issue is fixed, karen does not need to RN for 2.0.2
          Hide
          alkondratenko Aleksey Kondratenko (Inactive) added a comment -

          As can be seen above it is fixed.

          Show
          alkondratenko Aleksey Kondratenko (Inactive) added a comment - As can be seen above it is fixed.
          Hide
          kzeller kzeller added a comment -

          I add this to the 2.0.1 release notes as minor known issue to ignore. Is the message now fixed for 2.0.2?

          Show
          kzeller kzeller added a comment - I add this to the 2.0.1 release notes as minor known issue to ignore. Is the message now fixed for 2.0.2?
          Hide
          maria Maria McDuff (Inactive) added a comment -

          karen, are you finished documenting this?
          just flagging this for you for release note.

          Will assign to Ketaki for verification/closing.

          Thanks.

          Show
          maria Maria McDuff (Inactive) added a comment - karen, are you finished documenting this? just flagging this for you for release note. Will assign to Ketaki for verification/closing. Thanks.

            People

            • Assignee:
              ketaki Ketaki Gangal
              Reporter:
              ketaki Ketaki Gangal
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes