Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.0
-
Security Level: Public
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
For Gerrit Dashboard: MB-7542 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
24000,5 | MB-7542 Fix unset revision number on deserialization | 2.0.1 | couchdb | Status: MERGED | +2 | +1 |
24001,4 | MB-7542 Fix unset revision number on deserialization | 2.0.0 | couchdb | Status: MERGED | +2 | +1 |
24003,4 | MB-7542: Set seq_id to 1 if not set or as zero | 2.0.1 | membase-cli | Status: MERGED | +2 | +1 |
24034,2 | MB-7542: Set seq_id to 1 if not set or as zero | 2.0.0 | membase-cli | Status: MERGED | +2 | +1 |
24035,1 | MB-7542 Compactor bumps rev-num if it is zero | 2.0.0 | couchstore | Status: ABANDONED | +2 | 0 |
24036,5 | MB-7542 Compactor bumps rev-num if it is zero | 2.0.1 | couchstore | Status: ABANDONED | +2 | 0 |
24039,2 | Merge branch 'branch_2.0.0' | master | membase-cli | Status: ABANDONED | +2 | +1 |
24040,2 | Merge branch 'branch_2.0.0' into branch_2.0.1 | 2.0.1 | membase-cli | Status: MERGED | +2 | +1 |
24043,2 | Merge branch 'branch_2.0.0' | master | membase-cli | Status: MERGED | +2 | +1 |
24074,1 | MB-7542 Fix unset revision number on deserialization | 2.0.0 | couchdb | Status: ABANDONED | 0 | 0 |
24330,1 | Merge branch 'branch_2.0.1' | master | membase-cli | Status: MERGED | +2 | +1 |
26484,2 | Merge branch 'branch_2.0.1' | master | couchbase-cli | Status: ABANDONED | 0 | 0 |