Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.0-rc5, 3.7.1
Affects Version/s: None
Component/s: Replication
Labels:
- bkp

Backwards Compatibility:
Fully Compatible
Backport Requested:

v3.6
Sprint:
Repl 2017-11-13, Repl 2017-12-04
Linked BF Score:
0
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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).

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

(2 related to)

Assignee:: Judah Schvimer
Reporter:: Judah Schvimer
Participants:: Andy Schwerin, Githook User, Gregory McKeon, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Nov 02 2017 04:03:09 PM UTC
Updated:: Oct 30 2023 11:10:49 PM UTC
Resolved:: Nov 14 2017 11:25:55 PM UTC
Confidence Status Last Update:: 06/Nov/17 4:45 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates