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

GoXDCR Mutations Failed Resolution stat incorrect

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Fix
    • Major
    • 4.5.0
    • 4.1.0
    • UI, XDCR
    • None
    • Untriaged
    • Unknown

    Description

      This stat displayed in the UI from docs_failed_cr_source tracks the number of documents that were not replicated as they were not the winner of conflict resolution (e.g. they already exist on the destination cluster). It appears that this stat does not track accurately however:

      • Spin up 2 clusters, A and B.
      • Load beer-sample on A.
      • Enable replication from A.beer-sample -> B.default
      • Once all docs replicated, pause replication
      • Restart replication
      • On A, monitor Outgoing XDCR:
        When percentage complete reaches 100% (i.e. all docs have been checked), mutations failed resolution will sit at around 6400 (of 7303 total docs). This changes on subsequent runs with no obvious pattern.
      • On B, monitor Incoming XDCR:
        No sets are seen, implying that (as expected) all docs on B are at their latest revision. Therefore all docs on A should have been listed as failed.

      Attachments

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

        Activity

          People

            yu Yu Sui (Inactive)
            James Flather James Flather (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty