Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.1.1
Affects Version/s: None
Component/s: Sharding, Upgrade/Downgrade
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2018-06-18, Sharding 2018-07-02
Confidence Status:
None
Work Order:
3

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

The following needs to be done:
1. Create a list of tickets with code and tests to remove and mark them as “is depended on by” this ticket. This will assist the Upgrade/Downgrade Team in tracking progress.
2. Complete said tickets promptly.

3. Create a ticket identifying Sharding-related generic upgrade/downgrade references that the Upgrade/Downgrade team should update now that the 3.6-dependent references have been removed.

depends on

SERVER-34285 [post-branch] Remove FCV 3.6 switch logic in movePrimary

Closed

SERVER-34470 [post-branch] Make DatabaseVersion non-optional in database entries

Closed

SERVER-34550 [post-branch] Remove database versioning logic from setFCV command

Closed

SERVER-35390 Keep or update these Sharding-related FCV behaviors (tracking ticket)

Closed

SERVER-35391 Remove FCV logic in forceDatabaseRefresh()

Closed

SERVER-35392 Remove FCV logic concerning chunk history and afterClusterTime

Closed

SERVER-35395 Remove Sharding-related 3.6 to 4.0 upgrade/downgrade tests

Closed

SERVER-35396 Remove FCV 3.6 testing in create_database.js

Closed

(3 depends on)

Assignee:: Blake Oler
Reporter:: Blake Oler
Participants:: Blake Oler
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: May 21 2018 03:49:34 PM UTC
Updated:: Oct 29 2023 10:31:38 PM UTC
Resolved:: Jun 25 2018 06:59:42 PM UTC
Confidence Status Last Update:: 04/Jun/18 8:05 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates