Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
Fully Compatible
-
v3.6
-
Repl 2017-11-13, Repl 2017-12-04
-
0
Description
We allow rollbacks during upgrade since they run with the old rollback algorithm. rollbackViarefetchNoUUID cannot resync collections with UUIDs (see SERVER-31599), so this should occur during upgrade as well (though we do not have a repro of this exact case).
Attachments
Issue Links
- is related to
-
SERVER-31146 Rollback via refetch should only set collection options on local collection if they are non-empty
-
- Closed
-
-
SERVER-30413 Add function to set options.temp when resyncing collection metadata for rollback
-
- Closed
-
-
SERVER-31189 fassert if feature compatibility version changes during rollback
-
- Closed
-
-
SERVER-31599 Only allow rollbackViaRefetchNoUUID method when in FCV 3.4
-
- Closed
-
-
SERVER-31799 Run rollback fuzzer with upgrades
-
- Closed
-
- related to
-
SERVER-31881 Safe rollback does not properly remove collection temp status
-
- Closed
-
-
SERVER-31988 RollbackViaRefetch makes CollectionImpl validator out of sync with CollectionCatalogEntry
-
- Closed
-