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
    • Status: Closed
    • Major
    • Resolution: Fixed
    • Cheshire-Cat
    • 7.0.0
    • 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

          For Gerrit Dashboard: MB-45926
          # Subject Branch Project Status CR V

          Activity

            Expected upgrade behavior – new features are not generally available in a cluster that is being upgraded until all nodes are upgraded.

            https://docs.couchbase.com/server/current/install/upgrade.html#upgrade-faq

            Upgrade FAQ
            At which point in the upgrade process will the new features of the upgrade be available?
            Once every node in the cluster is upgraded to the target release, the new features of that release are available for use. Even if 90% of all nodes are upgraded, the cluster is still considered to be on the older revision, and newer features are unavailable.

            hyun-ju.vega Hyun-Ju Vega added a comment - Expected upgrade behavior – new features are not generally available in a cluster that is being upgraded until all nodes are upgraded. https://docs.couchbase.com/server/current/install/upgrade.html#upgrade-faq Upgrade FAQ At which point in the upgrade process will the new features of the upgrade be available? Once every node in the cluster is upgraded to the target release, the new features of that release are available for use. Even if 90% of all nodes are upgraded, the cluster is still considered to be on the older revision, and newer features are unavailable.
            rob.ashcom Rob Ashcom added a comment -

            That seems like the kind of thing we have to do all the time for mixed cluster. Pavel Blagodov??

            rob.ashcom Rob Ashcom added a comment - That seems like the kind of thing we have to do all the time for mixed cluster. Pavel Blagodov ??
            jliang John Liang added a comment -

            Rob Ashcom I see that Pavel updates the ETA. I am assuming he meant this is a UI bug. I am assigning this to UI team for now. Please assign it back to us if this is not a UI bug. Thanks.

            jliang John Liang added a comment - Rob Ashcom I see that Pavel updates the ETA. I am assuming he meant this is a UI bug. I am assigning this to UI team for now. Please assign it back to us if this is not a UI bug. Thanks.

            Build couchbase-server-7.0.0-5055 contains ns_server commit 9c213a9 with commit message:
            MB-45926: prevent explicit mode until cluster is fully upgraded

            build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.0-5055 contains ns_server commit 9c213a9 with commit message: MB-45926 : prevent explicit mode until cluster is fully upgraded

            Verified on 7.0.0-5177

            pavithra.mahamani Pavithra Mahamani added a comment - Verified on 7.0.0-5177

            People

              pavithra.mahamani Pavithra Mahamani
              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