Details

      Description

      scenarios which this might occur ( needs confirmation from engineering

      1- user upgraded from 1.8.x to 2.0.0 using offline upgrade ( cbupgrade )
      2- user has backed up data from 1.8.x or 2.0 customer and restored data to a 2.0 cluster
      3- user backing up data from a 2.0 cluster where data was restored from 1.8
      4- user has performed an online upgrade from 1.8.x to 2.x upgrade
      5- user has only 2.0 nodes and seq_id is set to 0 and if a node is failed over some items will have seq id set to 0 ( MB-7532 already merged )

      # Subject Project Status CR V
      For Gerrit Dashboard: &For+MB-7542=message:MB-7542

        Activity

        Hide
        bcui Bin Cui (Inactive) added a comment -

        Check into both 2.0 and 2.0.1 branch.

        Show
        bcui Bin Cui (Inactive) added a comment - Check into both 2.0 and 2.0.1 branch.
        Hide
        steve Steve Yen added a comment -

        Thanks Bin.

        Just recording another link here for 2.0.0 change: http://review.couchbase.org/#/c/24034/

        Show
        steve Steve Yen added a comment - Thanks Bin. Just recording another link here for 2.0.0 change: http://review.couchbase.org/#/c/24034/
        Hide
        TimSmith Tim Smith (Inactive) added a comment -

        I need to check for the possibility of an online fix for this. Could the new hotfix be applied on a freshly installed 2.0 node and then use that node to do a swap rebalance to replace a node without the hotfix? Would that enable an update to the new version without downtime, while handling load against the source cluster?

        Show
        TimSmith Tim Smith (Inactive) added a comment - I need to check for the possibility of an online fix for this. Could the new hotfix be applied on a freshly installed 2.0 node and then use that node to do a swap rebalance to replace a node without the hotfix? Would that enable an update to the new version without downtime, while handling load against the source cluster?
        Hide
        thuan Thuan Nguyen added a comment -

        Integrated in github-couchdb-preview #558 (See http://qa.hq.northscale.net/job/github-couchdb-preview/558/)
        MB-7542 Fix unset revision number on deserialization (Revision 59ac2586f515d9644fc47b934923e956eeed6fab)

        Result = SUCCESS
        Filipe David Borba Manana :
        Files :

        • src/couchdb/couch_db_updater.erl
        Show
        thuan Thuan Nguyen added a comment - Integrated in github-couchdb-preview #558 (See http://qa.hq.northscale.net/job/github-couchdb-preview/558/ ) MB-7542 Fix unset revision number on deserialization (Revision 59ac2586f515d9644fc47b934923e956eeed6fab) Result = SUCCESS Filipe David Borba Manana : Files : src/couchdb/couch_db_updater.erl
        Show
        plabee Phil Labee (Inactive) added a comment - http://hub.internal.couchbase.com/confluence/display/CR/MB-7542+*+seq_id+set+to+0+under+some+scenarios

          People

          • Assignee:
            bcui Bin Cui (Inactive)
            Reporter:
            farshid Farshid Ghods (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes