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

seq_id set to 0 under some scenarios

    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 )

        Attachments

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

          Activity

            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