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

[4TB, Magma, 1%]: XDCR replication never completes while there are 340M mutation pending on source side since hours and mutations are seen on destination but items counts doesn't change at destination.

    XMLWordPrintable

Details

    Description

      1. Create a 4 node cluster
      2. Create a 2 node XDCR remote cluster
      3. Create required buckets and collections.
      4. Create required buckets and collections on XDCR remote.
      5. Create 20000000 items sequentially
      6. Update 20000000 RandonKey keys to create 50 percent fragmentation
      7. Create 20000000 items sequentially
      8. Update 20000000 RandonKey keys to create 50 percent fragmentation
      9. Rebalance in with Loading of docs
      10. Rebalance Out with Loading of docs
      11. Rebalance In_Out with Loading of docs
      12. Swap with Loading of docs
      13. Stop the loading at Source side. Check XDCR items on the destination cluster. since so many hours there are continuous mutations coming but the items count are stuck at 186,879,889. Mutation reported at destination is around 50-100k/s. What are these mutations if the item counts aren't changing at the destination, Neil Huang ? Need your help in understanding.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MB-50240 [Magma, 2 replicas, 1%DGM]: XDCR Replication seems to be stuck on rebalance out 1 node on src cluster.

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-50074 Avg. initial XDCR rate in XDCR rebalance test dropped from 216K to 160K on build 7.1.0-1885

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. MB-41105 UI: XDCR Backfill

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MB-50340 XDCR - disable OSO if source bucket is using magma

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MB-50595 XDCR - investigate why "older node" message shows up

          • Major - Major loss of function.
          • Closed
          For Gerrit Dashboard: MB-50416
          # Subject Branch Project Status CR V
          169537,4 MB-50416: prevent duplicate push merge from locking up master goxdcr Status: MERGED +2 +1
          169648,2 MB-50416: ensure targetVBOpaque is populated for backfill pipeline master goxdcr Status: MERGED +2 +1

          Activity

            People

              ritesh.agarwal Ritesh Agarwal
              ritesh.agarwal Ritesh Agarwal
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty