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

Error replicating vbucket XX: {badmatch, {error,timeout}} on a bidirectional replication setup.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.1.0
    • Component/s: ns_server
    • Security Level: Public
    • Labels:
      None
    • Environment:
      2.0.1-170-rc

      Description

      -Load 40M items on cluster1, 2M items on cluster2

      • Setup a bidirectional replication between 2 clusters.
      • No front end load on either cluster , after loading the intial data.

      -After replicating 1.8M items , cluster2 replication shows errors w/ Badmatch timeout on serveral vbuckets.

      • On cluster1, seeing replication errors as "Failed to grab remote bucket info from any of known nodes" after replicating 25M items.

      Adding logs.

      Adding screenshots from both clusters.

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

        Activity

        Hide
        maria Maria McDuff (Inactive) added a comment -

        ketaki, shld this be a blocker? assigning critical for now... pls update this bug and assign to alk for investigation.
        also, is this sizing related, and does it recover?

        Show
        maria Maria McDuff (Inactive) added a comment - ketaki, shld this be a blocker? assigning critical for now... pls update this bug and assign to alk for investigation. also, is this sizing related, and does it recover?
        Hide
        maria Maria McDuff (Inactive) added a comment -

        assigning to alk k. issue is still there in 2.0.2

        Show
        maria Maria McDuff (Inactive) added a comment - assigning to alk k. issue is still there in 2.0.2
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        There is high chance that original issues is now addressed.

        We need fresh logs in order to see if we're hitting same issue or not and if not what is new issue.

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - There is high chance that original issues is now addressed. We need fresh logs in order to see if we're hitting same issue or not and if not what is new issue.
        Hide
        maria Maria McDuff (Inactive) added a comment -

        Alk, ok, we will get you fresh logs. thanks.

        Show
        maria Maria McDuff (Inactive) added a comment - Alk, ok, we will get you fresh logs. thanks.
        Hide
        ketaki Ketaki Gangal added a comment -

        Not able to reproduce this w/ 202-800 latest runs. Will reopen if seen again.

        Show
        ketaki Ketaki Gangal added a comment - Not able to reproduce this w/ 202-800 latest runs. Will reopen if seen again.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes