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

GoXDCR should not restart when it receives a NOT_MY_VBUCKET response

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • master, 4.1.2
    • 4.0.0, 4.1.0, 4.1.1
    • XDCR
    • None
    • Triaged
    • Yes

    Description

      GOXDCR does not have an easy way to handle NOT_MY_VBUCKET errors other than restarting. This is because GOXDCR caches vb server map in several components and it is not easy for GOXDCR to handle changes to the vb server map, which is what the NOT_MY_VBUCKET error typically indicates, when replication is still running.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MB-20093 [CLONE] GoXDCR should not restart when it receives a NOT_MY_VBUCKET response

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

          Activity

            People

              ritesh.motlani Ritesh Motlani (Inactive)
              merrick.huang Merrick Huang (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty