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

XDCR - should prevent explicit/migration mode until source cluster is fully upgraded

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 7.0.0
    • Cheshire-Cat
    • UI
    • Untriaged
    • 1
    • No

    Description

      When performing rolling upgrades, esp when a cluster is running in mixed mode where some nodes are < 7.0 and some are 7.0, XDCR does not prevent the users from activating collection-related modes/toggles.

      In the interest of safety, XDCR should enforce implicit mapping and not allow users to edit anything collection-related until it is confirmed that source cluster is fully upgraded.

      Also, it may make sense to check target cluster compatibility before allowing collection-related feature in replication settings to be set.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MB-45892 [Upgrade][XDCR][UI] Errors thrown while upgrading source cluster from 6.6.2 to 7.0.0

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

          Bug - A problem which impairs or prevents the functions of the product. MB-45951 XDCR - replication protection when running in mixed mode

          • Major - Major loss of function.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              pavithra.mahamani Pavithra Mahamani (Inactive)
              neil.huang Neil Huang
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty